macca-method 2.1.1 → 2.1.2

package/.agents/skills/brainstorm-rules/SKILL.md

@@ -20,6 +20,7 @@ Run as `@Fachri` (Tech Lead). Use the shared persona profile in `../_shared/refe
 You are **@Fachri — Tech Lead**. You protect consistency, quality, and security across the codebase.
 
 **Expertise:**
+
 - Coding standards and convention enforcement (TypeScript, ESLint, Prettier)
 - Git workflow, Conventional Commits, branching strategy
 - Secure coding practices (OWASP, input validation, secret handling)
@@ -39,20 +40,21 @@ This skill generates **rules.md**: a "code constitution" so AI works consistentl
 1. Ideally run this before coding starts.
 
 2. **Read existing project-context** before any user interaction:
-    - `project-context/architecture.md` — chosen tech stack and established patterns
-    - `project-context/PRD.md` — platform and constraints that affect coding standards
-    - `project-context/schema.md` — decisions about PII, retention, data protection
-    - `project-context/api.md` — auth contract, rate limiting, abuse controls
+   - `project-context/architecture.md` — chosen tech stack and established patterns
+   - `project-context/PRD.md` — platform and constraints that affect coding standards
+   - `project-context/schema.md` — decisions about PII, retention, data protection
+   - `project-context/api.md` — auth contract, rate limiting, abuse controls
 
 3. **Shared Runtime Setup** — before the interview (paths written as `../...` are relative to this SKILL.md's own folder, not the project's working directory):
-  - Read `../_shared/references/language-config.md`.
-  - Read `../_shared/references/config-mutation.md`.
-  - Read `../_shared/references/brainstorm-session.md`.
-  - Read `../_shared/references/scope-rules.md`.
-  - Use `languagePreferences.communication.normalized` for chat.
-  - Use `languagePreferences.documents.normalized` for the final `project-context/rules.md`.
-  - Apply `brainstormPreferences.discussionMode`, `recommendations`, and `discoveryDepth` using the shared session policy.
-  - For this skill: announce that there are 7 topics, ask for pacing (one by one / three at once / all at once), and ask for recommendation preference if it is not already stored.
+
+- Read `../_shared/references/language-config.md`.
+- Read `../_shared/references/config-mutation.md`.
+- Read `../_shared/references/brainstorm-session.md`.
+- Read `../_shared/references/scope-rules.md`.
+- Use `languagePreferences.communication.normalized` for chat.
+- Use `languagePreferences.documents.normalized` for the final `project-context/rules.md`.
+- Apply `brainstormPreferences.discussionMode`, `recommendations`, and `discoveryDepth` using the shared session policy.
+- For this skill: announce that there are 7 topics, ask for pacing (one by one / three at once / all at once), and ask for recommendation preference if it is not already stored.
 
 4. Run the interview in the selected mode. Wait for the answer before continuing.
 
@@ -65,18 +67,22 @@ This skill generates **rules.md**: a "code constitution" so AI works consistentl
 ## Interview Topics (7)
 
 ### 1. AI Persona & Tech Stack
-**Ask:** *"What main tech stack must this AI be skilled in?"*
+
+**Ask:** _"What main tech stack must this AI be skilled in?"_
 
 **Collect:**
+
 - List of technologies (for example TypeScript, React, Next.js 14, Prisma, PostgreSQL)
 - Prioritized libraries (for example TanStack Query, Zustand, React Hook Form, Zod)
 - Preferred patterns (for example functional components, Server Components, App Router)
 - Patterns to avoid (for example class components, Pages Router, `any` type)
 
 ### 2. Naming Conventions
-**Ask:** *"Which naming conventions apply: camelCase, PascalCase, snake_case?"*
+
+**Ask:** _"Which naming conventions apply: camelCase, PascalCase, snake_case?"_
 
 **Collect:**
+
 - Variables & functions: camelCase
 - React components: PascalCase
 - Files & folders: kebab-case or camelCase?
@@ -86,9 +92,11 @@ This skill generates **rules.md**: a "code constitution" so AI works consistentl
 - Database tables: snake_case, plural?
 
 ### 3. Code Style & Quality
-**Ask:** *"What code quality and cleanliness rules apply?"*
+
+**Ask:** _"What code quality and cleanliness rules apply?"_
 
 **Collect:**
+
 - TypeScript: strict mode? Avoid `any`? Avoid `enum` (use `as const`)?
 - `console.log`: forbidden in production?
 - Error handling: `try-catch` required? Prefer guard clauses (early return)?
@@ -101,9 +109,11 @@ This skill generates **rules.md**: a "code constitution" so AI works consistentl
 - What must never be simplified: trust-boundary validation, data-loss protection, accessibility basics, explicit requirements?
 
 ### 4. Security Rules
-**Ask:** *"Which security rules are mandatory: token storage, input sanitization, CORS, and so on?"*
+
+**Ask:** _"Which security rules are mandatory: token storage, input sanitization, CORS, and so on?"_
 
 **Collect:**
+
 - Token storage (httpOnly cookie, NOT localStorage)
 - User input sanitization before processing
 - Environment variable handling (do not hardcode, use `.env.example`)
@@ -119,9 +129,11 @@ This skill generates **rules.md**: a "code constitution" so AI works consistentl
 - If runtime credentials are managed: rotation and revocation expectations
 
 ### 5. AI Behavior Rules
-**Ask:** *"Are there special rules for AI? When should it ask first instead of assuming?"*
+
+**Ask:** _"Are there special rules for AI? When should it ask first instead of assuming?"_
 
 **Collect:**
+
 - Comment language (Indonesian/English)
 - Error message language (shown to users)
 - Ambiguity handling: ask first or make reasonable assumptions?
@@ -131,9 +143,11 @@ This skill generates **rules.md**: a "code constitution" so AI works consistentl
 - Must AI show reasoning before implementing complex changes?
 
 ### 6. Git Workflow
-**Ask:** *"What Git rules apply: commit format, branch naming, and so on?"*
+
+**Ask:** _"What Git rules apply: commit format, branch naming, and so on?"_
 
 **Collect:**
+
 - Commit message format: Conventional Commits? (`feat:`, `fix:`, `chore:`, etc.)
 - Branch naming: `feature/`, `fix/`, `chore/` prefix?
 - Squash merge or regular merge?
@@ -141,9 +155,11 @@ This skill generates **rules.md**: a "code constitution" so AI works consistentl
 - Are pre-commit hooks required (lint, test, audit)?
 
 ### 7. Linter, Formatter & Testing
-**Ask:** *"What quality tools are used: ESLint, Prettier, test framework?"*
+
+**Ask:** _"What quality tools are used: ESLint, Prettier, test framework?"_
 
 **Collect:**
+
 - ESLint: version? Rule set? (`eslint:recommended`, `@typescript-eslint/recommended`)
 - Prettier: options? (semicolon, quote style, print width)
 - `.editorconfig`: used?
@@ -162,6 +178,7 @@ Adapt only sections that are applicable and preserve every required contract fro
 ## Next Steps
 
 After rules.md is complete:
+
 1. Run `brainstorm-task` to create Task.md from all spec documents
 2. Then: use the `developer` skill to start implementation
 

package/.agents/skills/brainstorm-rules/assets/rules.template.md

@@ -1,6 +1,7 @@
 # Coding Standards (Rules)
 
 ## Document Role
+
 - **Source of Truth:** Coding standards, AI behavior constraints, and implementation security rules
 - **Primary Owner:** `brainstorm-rules`
 - **Out of Scope:** Product scope decisions, schema design, endpoint payload contracts, and task sequencing
@@ -8,26 +9,31 @@
 ---
 
 ## 1. AI Persona & Tech Stack
+
 > You are an expert developer in: [stack confirmed by architecture and user].
 
 **Prioritize:**
+
 - [Preferred patterns]
 
 **Avoid:**
+
 - [Patterns to avoid]
 
 ---
 
 ## 2. Naming Conventions
-| Type | Convention | Example |
-|------|------------|---------|
-| [Project symbol type] | [confirmed convention] | [stack-native example] |
-| Files & Folders | [confirmed convention] | [example] |
-| Persisted entities/fields | [datastore-native convention] | [example] |
+
+| Type                      | Convention                    | Example                |
+| ------------------------- | ----------------------------- | ---------------------- |
+| [Project symbol type]     | [confirmed convention]        | [stack-native example] |
+| Files & Folders           | [confirmed convention]        | [example]              |
+| Persisted entities/fields | [datastore-native convention] | [example]              |
 
 ---
 
 ## 3. Code Style & Quality
+
 - **Language-specific rules:** [rules confirmed for the selected language; omit inapplicable TypeScript examples]
 - **Production diagnostics:** [confirmed logging/telemetry rule]
 - **Error Handling:** [stack-native strategy confirmed by the project]
@@ -44,6 +50,7 @@ Add a language-specific example only when it communicates a confirmed rule bette
 ---
 
 ## 4. Security Rules
+
 > **MANDATORY:** Before writing code involving user input, auth, file upload, or database access — check at least these 4 items and explain them briefly: input validation, secret/token protection, safe queries, and access control.
 
 - **Token/Session Storage:** [project-specific decision; do not assume JWT or browser cookies]
@@ -55,6 +62,7 @@ Add a language-specific example only when it communicates a confirmed rule bette
 - **Dependencies:** Run the project's available dependency audit before release when network policy permits. Block [agreed threshold].
 
 ### Conditional Operational Rules
+
 - **Structured Logging:** [only when architecture defines observability]
 - **Migration Conventions:** [only when schema evolution applies]
 - **Feature Flag Lifecycle:** [only when architecture selects flags]
@@ -64,6 +72,7 @@ Add a language-specific example only when it communicates a confirmed rule bette
 ---
 
 ## 5. AI Behavior Rules
+
 - **Comment Language:** [Indonesian / English]
 - **Error Messages (user-facing):** [Indonesian / English]
 - **When Ambiguous:** Ask the user first; do not assume.
@@ -73,6 +82,7 @@ Add a language-specific example only when it communicates a confirmed rule bette
 - **Complex Implementations:** Show a plan/rationale before implementing.
 
 ## Rule Priority
+
 - **Priority Order:** Security → correctness → data protection → consistency → maintainability → convenience
 - If two rules seem to conflict, choose the higher-priority rule and note the trade-off.
 - If a local exception is needed, mark it clearly with a `tradeoff:` comment and explain the upgrade trigger.
@@ -80,23 +90,25 @@ Add a language-specific example only when it communicates a confirmed rule bette
 ---
 
 ## 6. Git Workflow
+
 **Commit format:** [confirmed workflow; omit this table if Conventional Commits was not selected].
 
-| Type | When |
-|------|------|
-| `feat:` | New feature |
-| `fix:` | Bug fix |
-| `chore:` | Maintenance (update deps, config) |
-| `docs:` | Documentation changes |
+| Type        | When                                          |
+| ----------- | --------------------------------------------- |
+| `feat:`     | New feature                                   |
+| `fix:`      | Bug fix                                       |
+| `chore:`    | Maintenance (update deps, config)             |
+| `docs:`     | Documentation changes                         |
 | `refactor:` | Code restructuring without feature/bug change |
-| `style:` | Formatting (no logic changes) |
-| `test:` | Add or fix tests |
-| `perf:` | Performance improvement |
-| `ci:` | CI/CD config changes |
+| `style:`    | Formatting (no logic changes)                 |
+| `test:`     | Add or fix tests                              |
+| `perf:`     | Performance improvement                       |
+| `ci:`       | CI/CD config changes                          |
 
 **Example:** `feat(auth): add Google OAuth login`
 
 **Branch naming:**
+
 - `feature/[feature-name]`
 - `fix/[bug-name]`
 - `chore/[task-name]`
@@ -104,6 +116,7 @@ Add a language-specific example only when it communicates a confirmed rule bette
 ---
 
 ## 7. Linter, Formatter & Testing
+
 - **Linter:** [existing tool/version/config; omit if none].
 - **Formatter:** [existing tool/options; omit if none].
 - **Editor settings:** [existing settings; omit if none].
@@ -117,11 +130,12 @@ Add a language-specific example only when it communicates a confirmed rule bette
 
 > Check this list before writing any code. Violating even one item = code rejected.
 
-| # | Forbidden | Why |
-|---|-----------|-----|
-| F-01 | Never hardcode or expose secrets | Security |
+| #     | Forbidden                                      | Why      |
+| ----- | ---------------------------------------------- | -------- |
+| F-01  | Never hardcode or expose secrets               | Security |
 | F-02+ | [Confirmed stack/project-specific prohibition] | [Reason] |
 
 ## Assumptions & Exceptions
+
 - [Assumption about team workflow or tooling]
 - [Temporary exception with owner / review trigger]

package/.agents/skills/brainstorm-schema/SKILL.md

@@ -20,6 +20,7 @@ Run as `@Fachri` (Tech Lead). Use the shared persona profile in `../_shared/refe
 You are **@Fachri — Tech Lead**, a **Senior Database Architect** who designs efficient, correct, secure data structures.
 
 **Expertise:**
+
 - Database modeling (relational and non-relational)
 - Normalization, intentional denormalization, and trade-offs
 - Indexing strategies based on real access patterns
@@ -53,8 +54,8 @@ Before any interview:
 1. Load after `architecture.md` is complete.
 
 2. **Read existing project-context**:
-    - `project-context/PRD.md` — features and business rules that determine tables
-    - `project-context/architecture.md` — tech stack, ORM, database conventions
+   - `project-context/PRD.md` — features and business rules that determine tables
+   - `project-context/architecture.md` — tech stack, ORM, database conventions
 
 3. If `.agents/developer-config.json` exists and `developerPreferences.scope = "frontend"`, DO NOT create `schema.md`. Explain that database and schema work is outside the current scope, and that backend dependencies should be documented only through the `api.md` consumer contract.
 
@@ -73,9 +74,11 @@ Before any interview:
 Ask all five topics using the chosen pacing mode. First classify the persistence model from `architecture.md` as relational, document, key-value, graph, event store, or mixed. Adapt terminology and output to that model.
 
 ### 1. Database Conventions
-*"Before tables, let's align on conventions. Any preferences?"*
+
+_"Before tables, let's align on conventions. Any preferences?"_
 
 Collect:
+
 - **Identity strategy:** primary key, document ID, aggregate/stream ID, graph ID, or key format?
 - **Naming:** datastore-native naming for tables, collections, keys, node labels, streams, and fields?
 - **Audit/version metadata:** timestamps, version/revision, event metadata, or none?
@@ -84,9 +87,11 @@ Collect:
 - **Retention:** How long is data stored? Any anonymization or archival schedule?
 
 ### 2. Entity/Storage List
-*"What tables, collections, aggregates, nodes, or stores are needed?"*
+
+_"What tables, collections, aggregates, nodes, or stores are needed?"_
 
 Collect by persistence model:
+
 - **Relational:** tables and junction tables
 - **Document:** collections, document roots, and embedded subdocuments
 - **Key-value:** key spaces, key format, and value shape
@@ -96,9 +101,11 @@ Collect by persistence model:
 - **Multi-tenant systems only:** tenant key/boundary, isolation enforcement, cross-tenant constraints, export/deletion, and partition strategy
 
 ### 3. Fields & Data Types
-*"For each data structure, list fields and datastore-native data types."*
+
+_"For each data structure, list fields and datastore-native data types."_
 
 Collect per datastore-native structure:
+
 - Field names and datastore-native types
 - Validation/constraints appropriate to the selected model
 - Which columns contain sensitive data/PII?
@@ -107,9 +114,11 @@ Collect per datastore-native structure:
 - Expected record/document/event volume, growth rate, payload size, and retention horizon where material
 
 ### 4. Relationships and Data Placement
-*"What relationships exist, and should related data use foreign keys, references, embedding, edges, or another datastore-native pattern?"*
+
+_"What relationships exist, and should related data use foreign keys, references, embedding, edges, or another datastore-native pattern?"_
 
 Collect:
+
 - **Relational:** cardinality, foreign-key owner, and cascade/set-null/restrict behavior
 - **Document:** embedding vs references, document growth, and update atomicity
 - **Key-value:** key composition, lookup direction, and secondary-index needs
@@ -119,9 +128,11 @@ Collect:
 - Concurrency model: transaction boundary, optimistic version, lock/contention policy, duplicate update protection, or equivalent
 
 ### 5. Indexes & Performance
-*"Which access patterns, filters, sorts, traversals, stream reads, or lookups must be efficient? What datastore-native indexes or projections support them?"*
+
+_"Which access patterns, filters, sorts, traversals, stream reads, or lookups must be efficient? What datastore-native indexes or projections support them?"_
 
 Collect:
+
 - Required reads/writes and expected scale
 - Datastore-native indexes, projections, partitioning, traversal, or caching needed for those access patterns
 - Consistency and latency expectations that constrain the design
@@ -150,5 +161,4 @@ Adapt only sections that are applicable and preserve every required contract fro
 - If the user has no table plan yet, suggest tables from PRD features and user stories.
 - Render the final document in the configured document language
 
-
 ---

package/.agents/skills/brainstorm-schema/assets/schema.template.md

@@ -1,11 +1,13 @@
 # Database Schema
 
 ## Document Role
+
 - **Source of Truth:** Data model and persistence contract
 - **Primary Owner:** `brainstorm-schema`
 - **Out of Scope:** Endpoint behavior, UI rules, and code-level implementation details
 
 ## Persistence Profile
+
 - **Model:** Relational / Document / Key-value / Graph / Event store / Mixed
 - **Identity Strategy:** [UUID / key format / aggregate ID / stream ID]
 - **Naming:** [datastore-native naming rules]
@@ -14,21 +16,25 @@
 - **Timezone:** [UTC/local/N/A]
 
 ## Entity / Storage Map
-| Data ID | Structure | Type | Purpose | Trace to |
-|---------|-----------|------|---------|----------|
-| DATA-01 | `[name]` | Table / Collection / Key Space / Node / Stream / Aggregate | [purpose] | `FEAT-01 / BR-01` |
+
+| Data ID | Structure | Type                                                       | Purpose   | Trace to          |
+| ------- | --------- | ---------------------------------------------------------- | --------- | ----------------- |
+| DATA-01 | `[name]`  | Table / Collection / Key Space / Node / Stream / Aggregate | [purpose] | `FEAT-01 / BR-01` |
 
 ## Global Data Protection
-| Structure/Field | Category | Protection | Retention | Notes |
-|-----------------|----------|------------|-----------|-------|
-| [users.email] | PII | [encrypt/mask/plain] | [retention rule] | [notes] |
+
+| Structure/Field | Category | Protection           | Retention        | Notes   |
+| --------------- | -------- | -------------------- | ---------------- | ------- |
+| [users.email]   | PII      | [encrypt/mask/plain] | [retention rule] | [notes] |
 
 ## Scale, Tenancy & Concurrency
+
 - **Expected Scale/Growth:** [records, payload, growth]
 - **Tenant Isolation:** [N/A or enforcement model]
 - **Concurrency Strategy:** [transaction/version/lock/idempotency]
 
 ## Schema Evolution & Migration
+
 - **Compatibility:** [backward/forward policy]
 - **Migration Order:** [expand/backfill/switch/contract or equivalent]
 - **Backfill & Validation:** [strategy]
@@ -40,19 +46,22 @@
 ## Relational Section (include only for relational or mixed)
 
 ### Table DATA-01: `[table_name]`
+
 > **Trace to:** [FEAT-01 / BR-01]
 > **PII:** Yes / No
 > **Retention:** [policy]
 
-| Column | Type | Nullable | Default | Constraint | Notes |
-|--------|------|----------|---------|------------|-------|
-| id | UUID | No | gen_random_uuid() | PRIMARY KEY | |
-| [column] | [type] | [Yes/No] | [default] | [constraint] | [notes] |
+| Column   | Type   | Nullable | Default           | Constraint   | Notes   |
+| -------- | ------ | -------- | ----------------- | ------------ | ------- |
+| id       | UUID   | No       | gen_random_uuid() | PRIMARY KEY  |         |
+| [column] | [type] | [Yes/No] | [default]         | [constraint] | [notes] |
 
 **Relationships:**
+
 - [One-to-many / many-to-many / delete rule]
 
 **Indexes:**
+
 - [column/index purpose]
 
 ---
@@ -60,6 +69,7 @@
 ## Document Section (include only for document or mixed)
 
 ### Collection DATA-01: `[collection_name]`
+
 > **Trace to:** [FEAT-01 / BR-01]
 
 - **Root Document Shape:** [summary]
@@ -72,6 +82,7 @@
 ## Key-Value Section (include only for key-value or mixed)
 
 ### Key Space DATA-01: `[keyspace_name]`
+
 > **Trace to:** [FEAT-01 / BR-01]
 
 - **Key Format:** [pattern]
@@ -83,6 +94,7 @@
 ## Graph Section (include only for graph or mixed)
 
 ### Node / Edge DATA-01: `[node_or_edge_name]`
+
 > **Trace to:** [FEAT-01 / BR-01]
 
 - **Node/Edge Type:** [type]
@@ -94,6 +106,7 @@
 ## Event Store Section (include only for event-store or mixed)
 
 ### Aggregate / Stream DATA-01: `[stream_name]`
+
 > **Trace to:** [FEAT-01 / BR-01]
 
 - **Aggregate Boundary:** [summary]
@@ -102,8 +115,10 @@
 - **Ordering / Versioning:** [rules]
 
 ## Not Yet Modeled / Deferred
+
 - [Data area intentionally not yet modeled]
 
 ## Assumptions & Open Questions
+
 - [Assumption about structures, relationships, or data rules]
 - [Question that needs user confirmation]

package/.agents/skills/brainstorm-styleguide/SKILL.md

@@ -20,6 +20,7 @@ Run as `@Akram` (UI/UX Designer). Use the shared persona profile in `../_shared/
 You are a **Senior UI/UX Designer** who builds scalable, consistent design systems.
 
 **Expertise:**
+
 - Building design tokens (color, typography, spacing)
 - Tailwind CSS, CSS Modules, utility-first approaches
 - Accessibility (WCAG) and responsive design principles
@@ -39,19 +40,19 @@ This skill generates **StyleGuide.md** through an interactive interview. It prev
 1. Run this after the PRD and architecture are clear, or when discussing UI design.
 
 2. **Read existing project-context** before any user interaction:
-    - `project-context/PRD.md` — target platforms and referenced UI patterns
-    - `project-context/architecture.md` — chosen frontend tech stack
-    - If `.agents/developer-config.json` exists, read `developerPreferences.scope`
+   - `project-context/PRD.md` — target platforms and referenced UI patterns
+   - `project-context/architecture.md` — chosen frontend tech stack
+   - If `.agents/developer-config.json` exists, read `developerPreferences.scope`
 
 3. **Shared Runtime Setup** — before the interview (paths written as `../...` are relative to this SKILL.md's own folder, not the project's working directory):
-    - Read `../_shared/references/language-config.md`.
-    - Read `../_shared/references/config-mutation.md`.
-    - Read `../_shared/references/brainstorm-session.md`.
-    - Read `../_shared/references/scope-rules.md`.
-    - Use `languagePreferences.communication.normalized` for chat.
-    - Use `languagePreferences.documents.normalized` for the final `project-context/StyleGuide.md`.
-    - Apply `brainstormPreferences.discussionMode`, `recommendations`, and `discoveryDepth` using the shared session policy.
-    - For this skill: announce that there are 7 topics, ask for pacing (one by one / three at once / all at once), and ask for recommendation preference if it is not already stored.
+   - Read `../_shared/references/language-config.md`.
+   - Read `../_shared/references/config-mutation.md`.
+   - Read `../_shared/references/brainstorm-session.md`.
+   - Read `../_shared/references/scope-rules.md`.
+   - Use `languagePreferences.communication.normalized` for chat.
+   - Use `languagePreferences.documents.normalized` for the final `project-context/StyleGuide.md`.
+   - Apply `brainstormPreferences.discussionMode`, `recommendations`, and `discoveryDepth` using the shared session policy.
+   - For this skill: announce that there are 8 topics, ask for pacing (one by one / three at once / all at once), and ask for recommendation preference if it is not already stored.
 
 4. If scope = `backend`, DO NOT create `StyleGuide.md`. Explain that UI work is outside the current scope.
 
@@ -66,18 +67,22 @@ This skill generates **StyleGuide.md** through an interactive interview. It prev
 ## Interview Topics (8)
 
 ### 1. CSS Framework
-**Ask:** *"What CSS framework is used: Tailwind, Bootstrap, or custom CSS?"*
+
+**Ask:** _"What CSS framework is used: Tailwind, Bootstrap, or custom CSS?"_
 
 **Collect:**
+
 - If Tailwind: v3 or v4?
 - If Bootstrap: preferred version?
 - Or CSS modules / styled-components / vanilla CSS?
 - Utility-first or component-based?
 
 ### 2. Color Palette
-**Ask:** *"What color scheme do you want? List primary, secondary, accent, and status colors."*
+
+**Ask:** _"What color scheme do you want? List primary, secondary, accent, and status colors."_
 
 **Collect:**
+
 - Primary color (brand)
 - Secondary color (accent)
 - Background color
@@ -87,9 +92,11 @@ This skill generates **StyleGuide.md** through an interactive interview. It prev
 - Hex/RGB codes if available
 
 ### 3. Typography
-**Ask:** *"What fonts do you want? Any difference between headings and body text?"*
+
+**Ask:** _"What fonts do you want? Any difference between headings and body text?"_
 
 **Collect:**
+
 - Heading font family (for example Inter, Poppins, Roboto)
 - Body font family
 - Font sizes for H1, H2, H3, H4, body, caption
@@ -97,18 +104,22 @@ This skill generates **StyleGuide.md** through an interactive interview. It prev
 - Google Fonts or custom fonts?
 
 ### 4. Spacing System
-**Ask:** *"What spacing scale do you want? Is the base unit 4px, 8px, or 16px?"*
+
+**Ask:** _"What spacing scale do you want? Is the base unit 4px, 8px, or 16px?"_
 
 **Collect:**
+
 - Base spacing unit (4px or 8px?)
 - Use default Tailwind scale or custom?
 - Padding/margin for containers, cards, buttons
 - Spacing between page sections
 
 ### 5. Component Style
-**Ask:** *"How should components look? For buttons, cards, and inputs, what border and shadow style do you want?"*
+
+**Ask:** _"How should components look? For buttons, cards, and inputs, what border and shadow style do you want?"_
 
 **Collect:**
+
 - Border radius (rounded-sm, rounded-md, rounded-full, square)
 - Button style (filled, outline, ghost) and sizes (sm, md, lg)
 - Card style (border, shadow, background)
@@ -117,25 +128,31 @@ This skill generates **StyleGuide.md** through an interactive interview. It prev
 - Transitions/animation: duration and easing (for example `150ms ease-in-out`)
 
 ### 6. Responsive & Breakpoints
-**Ask:** *"What responsive breakpoints are used? Mobile-first or desktop-first?"*
+
+**Ask:** _"What responsive breakpoints are used? Mobile-first or desktop-first?"_
 
 **Collect:**
+
 - Mobile-first (default) or desktop-first?
 - Breakpoint values (or use Tailwind defaults: sm:640, md:768, lg:1024, xl:1280)
 - Layout changes per breakpoint (for example sidebar collapses below md)
 
 ### 7. Iconography
-**Ask:** *"What icon library is used: Lucide, Heroicons, FontAwesome, or custom?"*
+
+**Ask:** _"What icon library is used: Lucide, Heroicons, FontAwesome, or custom?"_
 
 **Collect:**
+
 - Preferred icon library
 - Default icon size (16px, 20px, 24px)
 - Need custom SVG icons?
 
 ### 8. Accessibility, Localization & Operational States
-**Ask:** *"Which accessibility target and non-happy-path states must the UI support: loading, empty, error, forbidden, offline, reduced motion, keyboard, screen reader, or localization?"*
+
+**Ask:** _"Which accessibility target and non-happy-path states must the UI support: loading, empty, error, forbidden, offline, reduced motion, keyboard, screen reader, or localization?"_
 
 **Collect:**
+
 - Accessibility target from PRD (for example WCAG AA), keyboard order, visible focus, labels, contrast, touch targets, and reduced motion
 - Loading/skeleton, empty, error, disabled/read-only, permission-denied, offline, and partial-data behavior that applies to primary surfaces
 - Supported locales from PRD; text expansion, pluralization, date/number/currency/timezone formatting, and RTL only when relevant
@@ -152,6 +169,7 @@ Adapt only sections that are applicable and preserve every required contract fro
 ## Next Steps
 
 After StyleGuide.md is complete:
+
 1. Run `brainstorm-rules` to create coding standards
 2. Then: `brainstorm-task` to create Task.md