AI

Default Skills

Use generated app skills for repeated coding-agent workflows without bloating AGENTS.md.

By Guillermo Alvarez - Published Updated

Generated apps include a default GoLazy skill at .skills/golazy-framework/SKILL.md. It is an agent-facing workflow for adding or changing GoLazy application functionality.

Skills are not runtime code. They are durable instructions and supporting files for coding agents.

Default skill

The generated golazy-framework skill tells agents to:

  1. Read AGENTS.md and README.md first.
  2. Read only the skill references that match the task.
  3. Decide whether the change belongs in application code or in GoLazy framework packages.
  4. Plan by ownership boundary: service/domain first, dependency wiring second, route/controller/view third, tests last.

Its references cover application anatomy, routes, controllers, views, services, context helpers, assets, development commands, and testing expectations.

Skill layout

Use one skill directory per repeated workflow:

.skills/golazy-framework/SKILL.md
.skills/golazy-framework/references/framework-parts.md
.skills/golazy-framework/references/app-anatomy.md

The SKILL.md file is the entrypoint. Optional folders can sit beside it:

  • references/ for focused background documents
  • scripts/ for helper commands
  • templates/ for files that agents should reuse
  • examples/ for examples that are too long for the entrypoint

Keep each skill scoped. A skill that handles controller work should not also become the storage, deployment, and product-planning manual.

Add app-specific skills

Add a new skill when a workflow repeats and needs more detail than belongs in AGENTS.md. Good candidates are:

  • importing a domain-specific data format
  • deploying to the app's chosen platform
  • running a complex local service stack
  • editing a generated document or report format
  • operating an MCP module with app-specific safety rules

Keep secrets, one-off notes, and temporary debugging logs out of .skills. Skills should be safe to commit and useful to future work.

Keep skills aligned

Skills should point back to the latest GoLazy guides for framework behavior instead of copying large sections. Update the skill when generated app conventions change, especially around app structure, lazyapp.Config, asset generation, service lifecycle tasks, datasets, authentication, or MCP modules.