app-blueprint

app-blueprint is a skill for Claude Code, Codex from BostonOrange/claude-code-framework. It costs 19 tokens per session (937 once invoked), scanned A, original, MIT.

A command that turns a rough business-app idea into a structured JSON plan describing its users, records, workflow, permissions, and screens.

In plain words
What is it for?
Use it when planning or changing an internal Next.js business app, such as an approval tool, before generating the app.
Why use it?
It gives an app generator clear, consistent instructions instead of leaving important business details implicit.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when planning or changing an internal Next.js business app, such as an approval tool, before generating the app.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bostonorange/claude-code-framework/app-blueprint
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add BostonOrange/claude-code-framework --skill app-blueprint
Clone the repo
git clone --depth 1 https://github.com/BostonOrange/claude-code-framework

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for app-blueprint

README.md
[![agentmods](https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/app-blueprint/github.svg)](https://agentmods.dev/skills/bostonorange/claude-code-framework/app-blueprint)
Your own site
<a href="https://agentmods.dev/skills/bostonorange/claude-code-framework/app-blueprint"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/app-blueprint/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for app-blueprint

Your own site · 80×15
<a href="https://agentmods.dev/skills/bostonorange/claude-code-framework/app-blueprint"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/app-blueprint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 937 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.00937
Opus 5.5 $0.00008 $0.00375
Sonnet 5.5 $0.00004 $0.00187
Haiku 4.5 $0.00002 $0.00094

Measured 1mo ago against content hash d99920394b8a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

app-blueprint scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/app-blueprint/SKILL.md · 140 lines

How it starts

The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.

App Blueprint

Turn business intent into a concrete internal-app blueprint. Use this before generating or materially changing an internal Next.js business app.

Usage

/app-blueprint Build an approval app for supplier invoices
/app-blueprint docs/notes/invoice-workflow.md

If the user gives only a rough idea, produce the best blueprint you can and mark uncertain fields in openQuestions. Ask only for blockers that would make generation unsafe.

Process

  1. Read the prompt and any referenced files.
  2. Identify the core business workflow, users, records, file needs, audit trail, dashboards, and AI assist points.
  3. Normalize names to stable identifiers:
    • PascalCase for entity names.
    • camelCase for field names.
    • lower-kebab-case for workflow and view IDs.
  4. Keep the first pass small enough to generate:
    • Prefer 2-5 core entities.
    • Prefer explicit statuses over vague text fields.
    • Prefer role names that map to permissions.
  5. Write the result to docs/app-blueprint.json unless the user requested a different path.
  6. Report the blueprint path and any open questions.

Output Contract

Write valid JSON with this shape:

{
  "appName": "Supplier Invoice Desk",
  "summary": "Short operational description.",
  "usersAndRoles": [
    {
      "role": "financeManager",
      "displayName": "Finance Manager",
      "responsibilities": ["Approve invoices"],
      "authSource": "oidc"
    }
  ],
  "entities": [
    {
      "name": "Invoice",
      "description": "Supplier invoice awaiting review.",
      "fields": [
        {
          "name": "supplierName",
          "type": "string",
          "required": true,
          "unique": false,
          "sensitive": false,
          "notes": "Shown in lists and detail views."
        }
      ],
      "statuses": ["draft", "submitted", "approved", "rejected"],
      "relationships": [
        {
          "name": "attachments",
          "target": "FileObject",
          "cardinality": "many"
        }
      ]
    }
  ],
  "workflows": [
    {
      "id": "submit-invoice",
      "name": "Submit Invoice",
      "actorRoles": ["requester"],
      "entity": "Invoice",
      "fromStatuses": ["draft"],
      "toStatus": "submitted",
      "steps": ["Validate required fields", "Create audit event"]
    }
  ],
  "permissions": [
    {
      "role": "financeManager",
      "entity": "Invoice",
      "actions": ["read", "approve", "reject"]
    }
  ],
  "filesBlobNeeds": [
    {
      "entity": "Invoice",
      "purpose": "Store original invoice PDF",
      "allowedMimeTypes": ["application/pdf"],
      "maxSizeMb": 10,
      "retention": "Match finance record retention policy"
    }
  ],
  "auditEvents": [
    {
      "event": "invoice.approved",
      "actor": "financeManager",
      "entity": "Invoice",
      "payloadFields": ["invoiceId", "approvedAmount"]
    }
  ],
  "dashboardsViews": [
    {
      "id": "finance-queue",
      "name": "Finance Queue",
      "role": "financeManager",
      "type": "table",
      "entities": ["Invoice"],
      "filters": ["status", "supplierName"],
      "primaryActions": ["approve", "reject"]
    }
  ],
  "aiAssistPoints": [
    {
      "id": "invoice-review-assist",
      "name": "Invoice Review Assist",
      "trigger": "detail-view",
      "inputs": ["supplierName", "amount", "description"],
      "output": "Risk notes and recommended review checklist",
      "humanDecisionRequired": true
    }
  ],
  "openQuestions": []
}

Read the full file on GitHub · 140 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 140 lines · 19 tokens per session scan A d99920394b8a

Subscribe to this mod's changes

app-blueprint is a skill published in the GitHub repository BostonOrange/claude-code-framework (3 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 937 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens