agentleFS
shinprshinpr/nautilus/.agents/skills/blueprint-standards/SKILL.md

blueprint-standards

Skill7 starsChanged 3 months agoMITView on GitHub

Defines structural design artifact formats — information architecture, user flows, content model, brand direction, Visual Tokens, and AI interaction model. Use when creating or reviewing design artifacts that precede prototype generation.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Opportunity-grounded: Every major page or flow traces to a real opportunity or support need

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Blueprint Standards

Purpose

Blueprint artifacts define the structural and visual foundation that prototypes and downstream specs build upon.

They answer:

  • What pages and flows exist?
  • What data lives where?
  • What should the product feel like?
  • What concrete visual rules should AI tools reuse?

Artifact Overview

ArtifactQuestion It AnswersTemplate
Information ArchitectureWhat pages exist and how are they organized?references/ia-template.md
User FlowsHow do users move through the product to achieve goals?references/flow-template.md
Content ModelWhat data types exist and how do they relate?references/content-model-template.md
Brand DirectionWhat does the product look and feel like?references/brand-direction-template.md
AI Interaction ModelHow do users interact with AI features?references/ai-interaction-model-template.md

Relationship to Other Artifacts

docs/product/vision.md              ← Strategic intent
docs/product/design-principles.md   ← Trade-off resolutions
docs/product/personas/              ← Who uses it
docs/discovery/opportunities/       ← What problems to solve
docs/discovery/hypotheses/          ← What to validate
                ↓
docs/product/design/                ← Blueprint
                ↓
docs/discovery/prototypes/          ← Validation artifacts
                ↓
docs/prd/                           ← Delivery handoff

Scope

Blueprint defines: structure, navigation, data relationships, visual direction, Visual Tokens, interaction patterns
Blueprint defers: component APIs, production-ready design systems, pixel-perfect responsive specs

Key Principles

  • Opportunity-grounded: Every major page or flow traces to a real opportunity or support need
  • Persona-informed: Flows and terminology reflect actual users
  • Consistent across prototypes: Shared blueprint context prevents prototype-to-prototype drift
  • AI-readable: Visual Tokens and decisions are written in markdown so coding agents can consume them directly
  • Reusable downstream: PRDs, UI specs, and implementation can reference the same artifacts

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.