@c0x12c/ai-toolkit 1.15.0

package/templates/competitor-analysis.md

@@ -0,0 +1,60 @@
+# Competitor Analysis: [Competitor Name]
+
+**URL:**
+**Analyzed:** YYYY-MM-DD
+
+## Overview
+What do they do? Who are they for?
+
+## Pricing
+| Plan | Price | What You Get |
+|------|-------|--------------|
+| Free | $0 | |
+| Pro | $X/mo | |
+| Enterprise | $X/mo | |
+
+## Features
+| Feature | Have it? | Notes |
+|---------|----------|-------|
+| | Yes/No | |
+| | Yes/No | |
+| | Yes/No | |
+
+## What They Do Well
+1.
+2.
+3.
+
+## What They Do Poorly
+1.
+2.
+3.
+
+## User Reviews (G2, Capterra, Reddit, etc.)
+### What users love:
+-
+
+### What users hate:
+-
+
+## Traffic / Traction
+- Monthly visits (SimilarWeb):
+- Social followers:
+- Reviews count:
+- Founded:
+- Funding:
+
+## How They Get Users
+- [ ] SEO
+- [ ] Paid ads
+- [ ] Social media
+- [ ] Referrals
+- [ ] Partnerships
+- [ ] Content marketing
+- [ ] Other: ___
+
+## Positioning
+How do they describe themselves? What's their main message?
+
+## Our Opportunity
+What gap can we fill? How can we be different/better?

package/templates/content/AGENT_TEMPLATE.md

@@ -0,0 +1,47 @@
+---
+name: agent-name
+description: What this agent does. When to use it.
+tools: ["Read", "Grep", "Glob"]
+model: sonnet
+---
+
+You are [identity]. Your job is [mission].
+
+## Your Job
+
+- Thing 1
+- Thing 2
+- Thing 3
+
+## How You Think
+
+[1-2 sentences on experience and approach]
+
+Patterns you watch for:
+- Pattern 1
+- Pattern 2
+- Pattern 3
+
+## Process
+
+1. **Step** - What happens
+2. **Step** - What happens
+3. **Step** - What happens
+
+## Output Format
+
+### Section Name
+- [What goes here]
+
+### Section Name
+- [What goes here]
+
+### Verdict
+[FORMAT]
+[Explanation format]
+
+## Rules
+
+- Rule 1
+- Rule 2
+- Rule 3

package/templates/content/COMMAND_TEMPLATE.md

@@ -0,0 +1,27 @@
+---
+name: spartan:COMMAND-NAME
+description: What this command does in one line
+argument-hint: "[what the user passes]"
+---
+
+# Command Title: {{ args[0] | default: "fallback" }}
+
+One sentence — what this does and when to use it.
+
+## Steps
+
+### Phase Name
+1. First action
+2. Second action
+3. Third action
+
+### Next Phase
+4. Action
+5. Action
+6. Action
+
+## Rules
+
+- Rule 1
+- Rule 2
+- Rule 3

package/templates/content/RULE_TEMPLATE.md

@@ -0,0 +1,40 @@
+# Rule Name
+
+> Full guide: use `/skill-name` skill
+
+## The Rule
+
+State the rule clearly in 1-2 sentences.
+
+### WRONG
+
+```kotlin
+// bad code example
+```
+
+### CORRECT
+
+```kotlin
+// good code example
+```
+
+## Section 2 (if needed)
+
+### WRONG
+
+```kotlin
+// bad code
+```
+
+### CORRECT
+
+```kotlin
+// good code
+```
+
+## Quick Reference
+
+| Situation | Do This | Not This |
+|-----------|---------|----------|
+| Case 1 | Good | Bad |
+| Case 2 | Good | Bad |

package/templates/content/SKILL_TEMPLATE.md

@@ -0,0 +1,41 @@
+---
+name: skill-name
+description: What this skill does. When to use it.
+---
+
+# Skill Name
+
+One sentence — what this turns input into.
+
+## When to Use
+
+- Situation 1
+- Situation 2
+- Situation 3
+
+## Process
+
+### 1. First Step
+What to do. What to ask.
+
+### 2. Second Step
+What to produce.
+
+### 3. Third Step
+What to check.
+
+## Interaction Style
+
+How the skill talks to the user.
+- What it always does
+- What it never does
+
+## Rules
+
+- Rule 1
+- Rule 2
+- Rule 3
+
+## Output
+
+Where to save results. What format.

package/templates/design-config.md

@@ -0,0 +1,105 @@
+# Design Config: [Project Name]
+
+Per-project design system config. All design work reads this file first.
+
+**Location:** Save this to `.planning/design-config.md` in your project root.
+
+---
+
+## Brand Identity
+
+- **App name**: [your app or product name]
+- **Type**: [what kind of app — dashboard, SaaS, marketplace, etc.]
+- **Users**: [who uses it — roles, personas]
+- **Identity**: [3-5 words — e.g., "clean, professional, data-focused"]
+- **Theme**: [Light / Dark / Both]
+
+---
+
+## Color Palette
+
+Use ONLY these colors. Don't invent new ones. Don't use Tailwind defaults.
+
+| Role | Token | Value | Usage |
+|------|-------|-------|-------|
+| Background | `--color-bg` | [hex] | Page background |
+| Surface | `--color-surface` | [hex or rgba] | Card backgrounds |
+| Primary | `--color-primary` | [hex] | Buttons, active nav, links |
+| Primary Hover | `--color-primary-hover` | [hex] | Hover states |
+| Accent | `--color-accent` | [hex] | Highlights, badges (use sparingly) |
+| Text | `--color-text` | [hex] | Headlines, body text |
+| Text Secondary | `--color-text-secondary` | [hex] | Subtitles, descriptions |
+| Text Muted | `--color-text-muted` | [hex] | Labels, captions |
+| Border | `--color-border` | [hex or rgba] | Dividers, card edges |
+| Success | `--color-success` | [hex] | Positive states |
+| Warning | `--color-warning` | [hex] | Alert states |
+| Error | `--color-error` | [hex] | Error states |
+
+---
+
+## Typography
+
+- **Font**: [font name — e.g., "Inter", "Plus Jakarta Sans"]
+- **Headings weight**: [e.g., 600-700]
+- **Body weight**: [e.g., 400-500]
+- **Numbers**: [e.g., "tabular-nums" for data-heavy apps]
+
+---
+
+## Spacing & Radius
+
+- **Card radius**: [e.g., 12px]
+- **Button radius**: [e.g., 8px]
+- **Badge radius**: [e.g., 9999px (full round)]
+- **Shadows**: [e.g., "subtle slate-tinted: rgba(15, 23, 42, 0.04-0.10)" or "none — use glow effects"]
+
+---
+
+## Theme Files
+
+Where the actual CSS tokens live in the codebase:
+
+- **CSS Tokens**: [e.g., `src/styles/tokens.css` or `src/index.css`]
+- **Token prefix**: [e.g., `--color-` or `--color-brand-`]
+
+---
+
+## Design Personality
+
+[2-3 sentences. What feeling should the app give? Examples:]
+- "Dark, vibrant, premium. Glassmorphism cards, gradient orbs, glow effects."
+- "Warm, professional, data-focused. Clean tables, colorful stat cards, amber accents."
+- "Minimal, fast, developer-friendly. Monospace accents, high contrast, no decoration."
+
+---
+
+## Reference Apps
+
+Apps that have the quality level we want:
+
+| Reference | Why |
+|-----------|-----|
+| [app name] | [what to take from it — e.g., "clean data tables, good whitespace"] |
+| [app name] | [e.g., "sidebar nav, dark theme done right"] |
+
+---
+
+## Anti-References (What to NEVER Do)
+
+Things that would make our app look wrong:
+
+- [e.g., "NEVER light theme — this app is dark only"]
+- [e.g., "No playful/gamified aesthetic — we're B2B"]
+- [e.g., "No gradient blobs or decorative noise"]
+- [e.g., "No generic AI aesthetics"]
+
+---
+
+## Quick Reference
+
+| Question | Answer |
+|----------|--------|
+| What theme? | [Light / Dark / Both] |
+| Primary color? | [hex] |
+| Font? | [name] |
+| Token file? | [path] |

package/templates/design-doc.md

@@ -0,0 +1,207 @@
+# Design Document: [Feature Name]
+
+> **Workflow position:** Design is optional — use it for features with non-trivial UI work. It sits between Spec and Plan. After this passes the Design Gate, create the **implementation plan** (`implementation-plan.md`).
+>
+> ```
+> Epic → Spec → ► [Design] → Plan → Build → Review
+>                    ↑
+>               Design Gate
+> ```
+
+**Date**: [date]
+**Status**: Draft | In Review | Approved
+**Spec**: [path to spec, if exists]
+**Design Config**: [path to design-config.md, if exists]
+
+---
+
+## 0. Design References & Direction
+
+### Visual References
+
+| Reference | What to Take From It |
+|-----------|---------------------|
+| [screenshot/URL 1] | [e.g., "clean data table layout, good whitespace"] |
+| [screenshot/URL 2] | [e.g., "sidebar nav pattern, metric cards"] |
+
+### Design System
+- **Theme files**: [path to CSS tokens]
+- **Color palette**: [reference to design-config.md or existing design system]
+- **Font**: [font family from design-config]
+
+### Design Personality
+[Copy from design-config.md — or describe in 2-3 sentences]
+
+### Anti-References (What to Avoid)
+[Copy from design-config.md Anti-References section]
+
+---
+
+## 1. Design Brief
+
+### What are we designing?
+[One or two sentences. What screen, page, feature, or flow?]
+
+### Who's the user?
+[Target user persona]
+
+### Goal
+[What should the user be able to do after this is built?]
+
+### Platform
+[Desktop / Mobile / Both]
+
+---
+
+## 2. User Flows
+
+### Flow 1: [Flow Name]
+
+**Trigger**: [What starts this flow?]
+
+| Step | User Action | System Response | Screen |
+|------|-------------|-----------------|--------|
+| 1 | [action] | [response] | [screen name] |
+| 2 | [action] | [response] | [screen name] |
+
+### Edge Case Flows
+
+| Scenario | What Happens | Screen/State |
+|----------|--------------|--------------|
+| No data | [behavior] | Empty state |
+| Error | [behavior] | Error state |
+| Loading | [behavior] | Skeleton state |
+| Timeout | [behavior] | Retry state |
+
+---
+
+## 3. Screen Inventory
+
+| Screen | Purpose | States | Mobile Different? |
+|--------|---------|--------|-------------------|
+| [name] | [what it does] | loading, empty, data, error | Yes/No |
+
+---
+
+## 4. Component List
+
+| Component | Used In | Key Props | States |
+|-----------|---------|-----------|--------|
+| [name] | [screens] | [props] | [default, hover, loading, error, etc.] |
+
+---
+
+## 5. Section Zones
+
+Plan how sections alternate backgrounds for visual rhythm:
+
+| Section | Background | Mood |
+|---------|-----------|------|
+| [section name] | [color/token from design-config] | [e.g., "dramatic entry", "subtle shift"] |
+
+---
+
+## 6. Motion Plan
+
+What moves, how, and when:
+
+| Element | Animation | Trigger | Duration |
+|---------|-----------|---------|----------|
+| Section content | Fade up | Scroll into view | 0.6s ease |
+| Cards | Stagger fade | Scroll into view | 0.6s + 0.15s stagger |
+| Cards hover | Lift + shadow | Mouse hover | 0.2s ease |
+
+---
+
+## 7. Wireframes
+
+### [Screen Name]
+
+```
++------------------------------------------+
+|  Header / Nav                            |
++------------------------------------------+
+|                                           |
+|  [Main Content Area]                      |
+|                                           |
+|  +-------------+  +-------------+        |
+|  | Card 1      |  | Card 2      |        |
+|  +-------------+  +-------------+        |
+|                                           |
++------------------------------------------+
+```
+
+---
+
+## 8. Visual Design
+
+### Typography Scale
+
+| Role | Size | Weight | Letter-spacing |
+|------|------|--------|----------------|
+| H1 | [size] | [weight] | [spacing] |
+| H2 | [size] | [weight] | [spacing] |
+| H3 | [size] | [weight] | [spacing] |
+| Body | [size] | [weight] | normal |
+| Caption | [size] | [weight] | normal |
+
+---
+
+## 9. Component Specs
+
+### [Component Name]
+
+**Purpose**: [What this component does]
+
+**Props**:
+| Prop | Type | Required | Default | Description |
+|------|------|----------|---------|-------------|
+| [name] | [type] | [yes/no] | [default] | [what it does] |
+
+**States**:
+| State | Visual | Motion |
+|-------|--------|--------|
+| Default | [description] | None |
+| Hover | [description] | [animation] |
+| Active | [description] | [animation] |
+| Loading | [description] | Skeleton shimmer |
+| Error | [description] | [animation] |
+
+---
+
+## 10. Responsive Behavior
+
+| Breakpoint | Width | Layout Changes |
+|------------|-------|----------------|
+| Mobile | < 640px | Single column, hamburger nav, smaller type |
+| Tablet | 640-1024px | 2 columns, collapsed sidebars |
+| Desktop | > 1024px | Full layout, sidebars, 4+ columns |
+
+---
+
+## 11. Accessibility Checklist
+
+- [ ] Color contrast meets WCAG AA (4.5:1 for text, 3:1 for large text)
+- [ ] All interactive elements keyboard accessible
+- [ ] Focus order follows visual layout
+- [ ] Animations respect `prefers-reduced-motion`
+- [ ] Touch targets at least 44x44px on mobile
+- [ ] No information conveyed by color alone
+
+---
+
+## 12. Design Decisions Log
+
+| Decision | Options Considered | Chosen | Why |
+|----------|-------------------|--------|-----|
+| [decision] | [options] | [chosen] | [reasoning] |
+
+---
+
+## Tips
+
+- **Read design-config first** — every color and font must come from it
+- **Cover all states** — loading, empty, error are just as important as the happy path
+- **Be specific with copy** — use real feature names, not "Lorem ipsum"
+- **Think mobile first** — if it works at 375px, it'll work everywhere
+- **Component specs matter** — a dev should be able to build from just this doc

package/templates/epic.md

@@ -0,0 +1,100 @@
+# Epic: [Epic Name]
+
+> **Workflow position:** Epic is the starting point. After filling this in, write a **feature spec** (`feature-spec.md`) for each feature listed below.
+>
+> ```
+> ► Epic → Spec → [Design] → Plan → Build → Review
+> ```
+
+**Created**: [date]
+**Status**: planning | in-progress | done
+**Owner**: [who owns this]
+
+---
+
+## Why
+
+What are we building and why? What's the big picture?
+
+[2-3 sentences. Be specific about the outcome.]
+
+---
+
+## Success Criteria
+
+How do we know the epic is done?
+
+- [ ] [criteria 1]
+- [ ] [criteria 2]
+- [ ] [criteria 3]
+
+---
+
+## Features
+
+Ordered list of features. Each one becomes a spec → plan → build cycle.
+
+| # | Feature | Status | Spec | Plan | Depends On |
+|---|---------|--------|------|------|------------|
+| 1 | [feature name] | todo | — | — | — |
+| 2 | [feature name] | todo | — | — | #1 |
+| 3 | [feature name] | todo | — | — | #1, #2 |
+
+### Status values
+- `todo` — not started
+- `spec` — spec written, not built yet
+- `planned` — plan written, not built yet
+- `building` — currently being built
+- `done` — built, reviewed, merged
+- `skipped` — decided not to build
+
+---
+
+## Feature Briefs
+
+Short description of each feature. Enough to write a spec from.
+
+### Feature 1: [name]
+[2-3 sentences: what it does, why it matters, rough scope]
+
+### Feature 2: [name]
+[2-3 sentences]
+
+### Feature 3: [name]
+[2-3 sentences]
+
+---
+
+## Risks
+
+What could block us or go wrong?
+
+- [risk 1]: [how to handle]
+- [risk 2]: [how to handle]
+
+---
+
+## Notes
+
+- [note]
+
+---
+
+## Tips
+
+- **Start with why** — what problem does the whole epic solve?
+- **Order by dependency** — feature 2 shouldn't need feature 5
+- **Keep features small** — each one should be 1-3 days of work, not a month
+- **Be clear about scope** — what's in, what's out
+- **Feature briefs matter** — they're the seed for each spec session
+
+---
+
+## When to Use This vs Other Templates
+
+| Situation | Use |
+|-----------|-----|
+| Big feature set (3+ features, multi-week) | This epic template |
+| Single feature (1-3 days) | Skip epic, start with `feature-spec.md` |
+| Quick task (< 1 day) | Skip epic, use `/spartan:spec` → `/spartan:build` |
+| Product-level vision doc for stakeholders | Use `prd-template.md` instead |