3.1.1 Ai Dev Workflows

This skill defines the standards for working effectively with AI coding assistants (Antigravity, Firebase Studio, v0.dev, Bolt.new) to maximize code quality, minimize hallucination, and establish repeatable automation patterns.

1. Skill Authoring Standards

Goal: Every skill file must be consistent, discoverable, and actionable.

• File Structure: Each skill lives in .agent/skills/<NN>_<snake_case_name>/SKILL.md. The numbered prefix (01–99) establishes a logical reading order.
• YAML Frontmatter: Required fields: name (human-readable title with ID prefix), description (50-150 character summary for tooling), version (SemVer).
• Content Format: Use numbered sections (## 1. Section Title). Each section has a bold Goal: line followed by bulleted instructions. Include code snippets where they add clarity.
• Scope: Each skill covers one domain. Avoid overlapping responsibilities between skills. Cross-reference related skills by ID number (e.g., "See Skill 05 for PWA caching strategies").
• Versioning: Increment version when content changes meaningfully. PATCH for typo/clarification fixes. MINOR for added sections. MAJOR for restructuring.

2. Effective Prompting Patterns

Goal: Get high-quality, production-ready code on the first generation.

• Context Loading: Always reference relevant skills before starting implementation. Say: "Read Skill 04 and apply its design token standards" rather than re-describing the standards.
• Specificity: Avoid "make it look good." Instead: "Use a dark theme with --color-surface: hsl(230, 20%, 10%), glassmorphism cards with backdrop-filter: blur(16px), and Inter font at 16px base."
• Constraints First: State what NOT to do before what to do. "Do not use Tailwind. Do not use inline styles. Use CSS custom properties for all colors." This prevents the most common deviations.
• Incremental Building: Build in layers: (1) data model/types, (2) CSS design system, (3) components, (4) page assembly, (5) interactions. Review each layer before proceeding.
• Verification Requests: End prompts with specific verification steps: "After building, run the dev server and use the browser tool to verify the layout at 375px and 1280px widths."