Skills

Skills are your rules for the AI: your brand, your tech stack, how you write. Add them once, and Flowmaps gives them to Claude every time it writes build prompts or builds a feature. The AI then builds the way you want, without you repeating yourself.

Open it

Click Skills in the sidebar.

Add a skill

Click + New skill, or start from an example: Brand guidelines, Tech stack or Writing style. Each skill has:

• Name: short, lowercase with dashes, like tech-stack.
• Applies to: All ventures (like your brand), or only one venture (like the tech stack of one product).
• When should Claude use this? One sentence, like "Use when building anything users see."
• Instructions: what Claude should do. Be concrete: colors, fonts, frameworks, words to use or avoid. You can use Markdown and check it under Preview.

Click Save skill.

The setup skill of a venture

When you create a venture, your answer to How will you build it? becomes a skill on that venture, named after it (like tech-setup-adonboard-…). Change it here if you switch tools later, and new build prompts follow.

Switch skills on and off

Untick On to pause a skill without deleting it. Only skills that are on go along with your builds.

Where your skills are used

• Build prompts: when you click Generate under Build prompts, Claude takes your skills into account.
• Building with the flowmaps command or inside Claude: your skills are added to the build instructions under "Follow these skills".

Each build gets the skills for all ventures, plus the skills for that venture.

Use skills directly in Claude

Skills use Claude's standard SKILL.md format, so they work outside Flowmaps too:

• Import SKILL.md to bring in a skill you already have.
• Click SKILL.md next to a skill to download it. In Claude Code, put it in your project at .claude/skills/<name>/SKILL.md.

Example

You add a skill tech-stack for only LayerloopsData:

When should Claude use this? Use when writing code for LayerloopsData.

Instructions: Build with Next.js and TypeScript, Supabase for the database and login, Tailwind for styling, Stripe for payments. Don't add other services without asking.

Next time you generate build prompts for a LayerloopsData feature, they use exactly that stack. When you build it, Claude gets the same rules and follows them.