get-shit-pretty 0.7.0 → 0.7.3

package/gsp/skills/gsp-start/questioning.md

@@ -1,87 +0,0 @@
-# Brief-Gathering Techniques
-
-## Purpose
-Guide brief-gathering conversations — used by `/gsp-start` for both brand briefs and project briefs.
-
----
-
-## Core Rules
-
-**One decision per question.** Every question must be its own `AskUserQuestion` call. Never group multiple questions into a single message. Ask one thing, wait for the answer, use it to inform the next question.
-
-**Never re-ask what the user already answered.** If information was gathered in a prior phase and is available in BRIEF.md or other artifacts, use it — don't ask again. If you need to validate stale information, confirm it ("I see X from earlier — still accurate?") rather than asking from scratch. Each phase reads the prior phase's output; the user should never feel like they're repeating themselves.
-
----
-
-## Question Flow
-
-### Phase 1: Context (Who & Why)
-Start broad, then narrow. Each is a separate `AskUserQuestion`.
-
-1. **What** is this project? (app, website, rebrand, campaign)
-2. **Who** is it for? (audience demographics, psychographics)
-3. **Why** does it exist? (business goal, user need)
-4. **What problem** does it solve?
-
-### Phase 2: Brand (Identity & Voice)
-5. Is there an **existing brand** to work with?
-6. Three words that describe the **brand personality**
-7. **Brands you admire** (and why)
-8. **Styles to avoid** (and why)
-
-### Phase 3: Scope (What & Where)
-9. **Platforms:** Web, iOS, Android, all?
-10. **Tech stack** preferences? (React, Swift, Flutter, etc.)
-11. **Key screens/pages** needed?
-12. **Accessibility level:** WCAG A, AA, or AAA?
-
-### Phase 4: Constraints (Limits & Realities)
-13. **Timeline:** When does this need to ship?
-14. **Budget:** Any constraints on tools, licensing, assets?
-15. **Existing assets:** Logo, brand guide, content, photography?
-16. **Team:** Who will implement? (devs, designers, solo)
-
-### Phase 5: Success (How We Know)
-17. **What does success look like?** (metrics, feelings, outcomes)
-18. **Biggest risk** if we get this wrong?
-
----
-
-## Questioning Techniques
-
-### One at a Time
-Ask each question as its own `AskUserQuestion` call. Wait for the answer before asking the next. Use each answer to decide whether to skip, reframe, or drill into the next question.
-
-### Adapt and Skip
-Don't follow the list rigidly. If an early answer reveals enough context, skip later questions. If an answer is surprising, follow up before moving on. The sequence is a guide, not a script.
-
-### Follow-Up Patterns
-- **"Tell me more about..."** — When an answer is surface-level
-- **"What would that look like?"** — When an answer is abstract
-- **"Why is that important?"** — To uncover underlying needs
-- **"What if we couldn't do that?"** — To test assumptions
-
-### Inference Over Interrogation
-Don't ask what you can infer:
-- If they say "fintech app for Gen Z" → infer mobile-first, modern aesthetic
-- If they say "enterprise dashboard" → infer data-dense, professional
-- State your inferences and let them correct
-
-### Handling Vague Answers
-- Use `AskUserQuestion` with 2-3 concrete options instead of open-ended re-asks
-- Each option should have a clear **label**, a **description** explaining what it means, and optionally a **preview** showing what it looks like in practice
-- Example: instead of "What style do you want?", use `AskUserQuestion` with options like "Minimal & clean" (description: "Lots of white space, restrained palette") vs "Bold & expressive" (description: "Saturated colors, strong typography")
-- Reserve prose questions for open-ended exploration where you genuinely don't know the option space
-
-### When to Use `AskUserQuestion` vs Prose
-- **Always use `AskUserQuestion`** — this is the default for every user-facing question
-- **Prose is only for** follow-up clarifications where the answer space is truly unbounded and you cannot write meaningful options
-- **Rule of thumb:** if you can write 2-4 meaningful options with descriptions, use `AskUserQuestion`. If you'd be guessing at what the options should be, still use `AskUserQuestion` with an open-ended framing.
-
-### Knowing When You Have Enough
-A brief is complete when you can answer:
-- [ ] Who is this for and what do they need?
-- [ ] What does the brand feel like?
-- [ ] What are we building and on what platforms?
-- [ ] What are the hard constraints?
-- [ ] How will we measure success?

package/gsp/templates/phases/launch.md

@@ -1,55 +0,0 @@
-# Launch Campaign
-
-## Project: {PROJECT_NAME}
-**Date:** {DATE}
-
----
-
-> This phase produces 6 chunks + INDEX.md in the `launch/` directory.
-
-## Chunk Mapping
-
-| Chunk File | Content |
-|-----------|---------|
-| `campaign-strategy.md` | Objective, audience, key message, tone, channels |
-| `digital-ads.md` | Google Ads + Meta/Instagram + TikTok (all formats and A/B variants) |
-| `email-sequences.md` | All sequences with subject lines, body copy, CTAs |
-| `landing-page.md` | Full page structure with above-fold and sections |
-| `social-media.md` | Per-platform posts with copy, visual direction, hashtags |
-| `sales-content.md` | Sales enablement + content marketing combined |
-
-## Content Reference
-
-Each chunk follows the standard chunk format. Below is the structural reference for what each chunk should contain:
-
-### campaign-strategy.md
-- **Objective:** campaign goal
-- **Target audience:** segments
-- **Key message:** core message
-- **Tone:** voice and tone for campaign
-- **Channels:** distribution strategy
-
-### digital-ads.md
-- **Google Ads:** Format, Headline, Description, CTA, Visual Direction
-- **Meta / Instagram:** Format, Copy, Visual Direction, CTA, A/B Variant
-- **TikTok:** Format, Hook, Copy, Visual Direction
-
-### email-sequences.md
-- **Welcome series:** 3 emails with subject, purpose, body copy, CTA
-- **Promotional:** email specs
-- **Re-engagement:** email specs
-
-### landing-page.md
-- **Headline:** main headline
-- **Subhead:** supporting copy
-- **Hero:** visual direction
-- **CTA:** primary call to action
-- **Social proof:** approach
-- Full section-by-section page structure
-
-### social-media.md
-- Per-platform table: Platform, Post Type, Copy, Visual Direction, Hashtags
-
-### sales-content.md
-- **Sales enablement:** materials list with descriptions
-- **Content marketing:** content pieces with topics and formats