skill-optimization
Skill Content Optimization
Core Philosophy
- Evidence-Based: Grounded in prompt engineering research, applied to skill authoring
- Concrete: Each pattern provides detection criteria and transform methods
- Structure-Focused: Optimizes expression and organization; domain knowledge remains unchanged
Content Optimization Patterns
P1: Critical (Must Fix)
Issues that directly reduce LLM execution accuracy when consuming the skill.
BP-001: Negative Instructions → Positive Form
| Detection | Transform |
|---|---|
| "don't", "do not", "never", "avoid" in skill instructions | Reframe as positive directive with equivalent constraint. Exception: Negative form is permitted only when ALL 4 conditions are met: (1) violation destroys state in a single step, (2) caller or subsequent steps cannot normally recover, (3) the constraint is operational/procedural, not a quality policy or role boundary, (4) positive rewording would expand or blur the target scope. If any condition is not met, rewrite in positive form. |
More from shinpr/ai-coding-project-boilerplate
documentation-criteria
Guides PRD, ADR, Design Doc, UI Spec, and Work Plan creation. Use when creating or reviewing technical documents, or when "UI spec/screen design/component decomposition" is mentioned.
12project-context
Provides project-specific prerequisites for AI execution accuracy. Use when checking project structure.
10coding-standards
Detects code smells, anti-patterns, and readability issues. Use when implementing features, reviewing code, or refactoring.
9technical-spec
Defines environment variables, architecture design, and build/test commands. Use when configuring environment or designing architecture.
9task-analyzer
Analyzes task essence and selects appropriate skills. Returns scale estimates and metadata. Use when starting tasks or selecting skills.
9typescript-rules
Applies type safety and error handling rules. Enforces no-any policy and type guards. Use when implementing TypeScript or reviewing types.
9