swan-design

Generate technical specifications with ASCII diagrams and Grove voice.

5|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/AutumnsGrove/Lattice --skill swan-design
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: swan-design
Source: https://github.com/AutumnsGrove/Lattice/tree/main/.claude/skills/swan-design
Command: npx skills add https://github.com/AutumnsGrove/Lattice --skill swan-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of high-quality technical specifications, ensuring clarity, consistency, and adherence to the Grove's unique voice and standards.

Core Features & Use Cases

  • Structured Specification Writing: Guides users through a phased approach (Vision, Sketch, Refine, Polish, Launch) for comprehensive documentation.
  • Grove Voice & Formatting: Enforces specific writing style, anti-patterns, and formatting rules unique to the Grove ecosystem.
  • Use Case: When a new feature is proposed, use this Skill to generate a detailed technical specification that includes architecture diagrams, API definitions, and clear implementation steps, all while maintaining the project's distinct narrative style.

Quick Start

Use the swan-design skill to write a spec for the new user authentication system.

Frequently Asked Questions about swan-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a technical specification with structured phases?▼

To write a technical specification with structured phases, follow a five-step process: Vision, Sketch, Refine, Polish, and Launch. This phased design approach ensures comprehensive documentation by guiding you gradually from initial architecture concepts to finalized specifications.

What is the Grove voice convention for technical writing?▼

The Grove voice convention for technical writing is a specific narrative style that enforces unique formatting rules, anti-patterns, and writing standards. It transforms standard technical plans into storybook entries, ensuring clarity and consistency across project documentation.

Can I include ASCII art and flow diagrams in my technical documentation?▼

Yes, you can include ASCII art and flow diagrams in your technical documentation. This approach uses ASCII artistry to generate elegant visual representations of architecture and flow directly within your text-based technical specifications.

What is the best way to review and transform technical plans into storybook entries?▼

The best way to review and transform technical plans into storybook entries is to apply the Grove voice conventions alongside ASCII artistry. This method converts standard plans into narrative-driven specifications while maintaining strict adherence to project formatting rules.

Does this specification writing process require any external dependencies?▼

No, this specification writing process does not require external dependencies. It operates independently using internal references to enforce its specific writing style, anti-patterns, and formatting rules for generating your technical documentation.