Manzanita-Research

Build frontend interfaces for Manzanita Research — warm, editorial, California-rooted design for music tools and brand pages. React + Tailwind. Use when building web components, pages, landing pages, dashboards, plugin UIs, or any web interface for Manzanita projects.

Manzanita Research visual identity tokens — colors, typography, and texture direction. Apply these whenever building any visual interface (web, terminal, print, slides) for a Manzanita project. Other design skills (frontend-design, tui-design) reference this as their brand layer. Use this skill when you need the specific color values, font settings, or visual identity rules for Manzanita Research, even if you're not using one of the design skills.

Write in the Manzanita Research voice — warm, grounded, direct, never corporate. Use for any prose output: READMEs, marketing pages, social posts, changelogs, error messages, UI copy, blog posts, or any text that carries the brand.

Build frontend interfaces with intentional, craft-level design — editorial layout, expressive typography, textured atmosphere, and considered motion. React + Tailwind. Use when building web components, pages, landing pages, dashboards, plugin UIs, or any web interface. For Manzanita Research projects, this skill works alongside brand-tokens for the visual identity layer.

Create or update a PITCH.md — a plain-text pitch for your project that tells the story, communicates the vision, and makes the case. Not a README (that's for users). Not a pitch deck (that's theater). This is the argument for why this thing should exist, written clearly enough that it speaks for itself.

Build terminal user interfaces with craft and intention — information architecture, interaction design, and visual hierarchy in monospace. Go + Bubble Tea + Lip Gloss. Use when building TUI dashboards, interactive CLIs, terminal menus, status displays, or any terminal interface. For Manzanita Research projects, this skill works alongside brand-tokens for the color palette.

Generate image prompts for Manzanita Research hero images. Reads the current repo to infer what the project is, then writes prompts you can paste into Flora or any text-to-image tool. Eco-futurist, feminine, 1980s-meets-2180s California.

Spin up parallel divergent research agents to explore an idea from every angle. Use when the user has a braindump, PRD, seed, concept, or half-formed idea they want explored. Triggers on "idea girlie", "divergent research", "explore this idea", "brainstorm this", "spin up researchers", "what are the options", "research this from different angles", "give me wild ideas", "I need divergent thinking on this", "explore the possibility space", or any variation of wanting parallel creative/strategic research on a concept.

Search past idea-girlie research across all projects. Use when the user asks "have we researched this before", "what do we know about X", "find that research on Y", "recall", "pull up past research", "what did the idea girlies say about", or any variation of wanting to search the centralized knowledge base for prior research sessions.

Set up Linear for solo or small-team multi-repo work. Creates the one-team + product-label-group structure, discovers repos from GitHub, and builds custom views. Use when someone says "set up linear", "organize my linear", "I have too many repos", "how should I structure linear", "set up labels for my repos", or any variation of configuring Linear for multi-project work.

Generate a "building in public" update from recent Linear activity and freeform notes. Use when the user wants to share what they've shipped, write a dev update, post about recent work, or draft a "here's what we built" post. Triggers on "farm-stand", "what did I ship", "write an update", "building in public", "what have I been working on", "status update", "what's new", "what did we release", or any variation of wanting to summarize recent work for an audience.

Migrate a repo's GSD (.planning/) data to Linear issues. Use this skill when the user wants to transition from GSD to Linear, move planning data to Linear, import GSD phases into Linear, or asks about migrating their .planning/ directory. Also triggers on "migrate to linear", "move GSD to linear", "import planning to linear", or any mention of converting GSD phases/plans into Linear issues. Only relevant for repos that have a .planning/ directory.

Capture project ideas as lightweight Linear issues before they become real repos. Use when the user floats an idea, riffs on a concept, says "what if we...", "we should build...", "imagine if...", "idea:", or any variation of sharing a project idea they're not ready to commit to. Also triggers on "catch this idea", "pin this thought", "seed this", or "add to the wall". This is the sticky-note-on-the-studio-wall skill.

Track work in Linear via linctl without leaving your editor. Use this skill whenever the user describes work to be done — feature requests, bugs, improvements, things to build, things to fix. Also use it when the user explicitly asks to create an issue, check what's open, or work on a ticket. Triggers on intent like "let's build X", "we need to fix Y", "add support for Z", "X is broken", "it would be nice if", "what's ready", "what should I work on next", "what's on the board", as well as explicit "create an issue". If this skill is loaded in your context, use Linear for task tracking.