# Skills: Your Rules for the AI Builder

> 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 p

Canonical: https://flowmaps.app/docs/skills

Plan

# Skills

Last updated: October 2026

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**.

brand-guidelines On

Use when building anything users see.

\- Primary color #1e1b1a

\- Friendly, short sentences

\- Never more than one call to action

## 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](https://flowmaps.app/docs/command-line)** or **[inside Claude](https://flowmaps.app/docs/claude-connection):** 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.

[← PreviousFlags](https://flowmaps.app/docs/flags)[Next →Import a project you're already building](https://flowmaps.app/docs/import-project)

Try it on your own app idea

Flowmaps is free to start, and new accounts get 7 days of Pro. No credit card.

[Start free](https://flowmaps.app/login?new=1)
