| name | general |
| description | General execution skill for docs-first implementation, error handling, and repository-wide consistency |
| license | MIT |
| compatibility | opencode |
| metadata | {"audience":"developers","workflow":"general"} |
General Skill
Default Behavior
Use this skill when the task spans multiple areas or no narrower skill is a better fit.
Prefer Another Skill When
- the task is clearly frontend-only, backend-only, devops-only, or docs-only
- the task is specifically about subagent orchestration or memory usage
Core Operating Rules
- Read enough context before changing anything.
- Prefer official docs over memory or guesswork.
- Keep changes focused and internally consistent.
- Update user-facing docs when behavior or setup changes.
- Verify the result with the best checks available.
Research Rule
- Use
context7 for official documentation.
- Use
gh_grep for implementation patterns.
- Use
webfetch when the needed documentation is outside MCP.
Repository Standards
- Keep structure simple.
- Avoid unnecessary new folders and files.
- Maintain naming consistency.
- Keep config, prompts, and docs aligned.
Environment Rule
- Never read or edit
.env directly.
- When environment requirements change, create or update
.env.example.
- Assume the documented keys also exist in
.env.
Session Rule
If prior session context exists, use it to continue rather than restarting from scratch.
Done Criteria
- the task is implemented, not merely analyzed
- related docs are current
- configuration drift has not been introduced