siddheshbmane

Blueprints Skill — AI skill for Claude Code

AI community

Cross-tool Agent Skill (SKILL.md) that turns any AI coding tool — OpenCode, Claude Code, Codex, Gemini, Cursor — into a docs-first, staging-first SaaS product builder with intake questionnaires, user.

How to install Blueprints Skill

This entry records only its repository, not the path inside it, so there is no exact command to give. Open siddheshbmane/blueprints-skill and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Blueprints Skill does

Cross-tool Agent Skill (SKILL.md) that turns any AI coding tool — OpenCode, Claude Code, Codex, Gemini, Cursor — into a docs-first, staging-first SaaS product builder with intake questionnaires, user-flow E2E, and an Ask-User production gate.

Alternatives in AI

  • Cumora — Where agent teams gather 3.2k ★
  • Token Monitor — Local-first desktop widget for tracking token usage, costs, and limits across 32+ AI coding tools—including Cl 1.8k ★
  • Claw Empire — Command Your AI Agent Empire from the CEO Desk — A local-first AI agent office simulator that orchestrates CLI 1.1k ★

README

Blueprints — Cross-Tool Product Development Skill

[![skills.sh](https://skills.sh/b/siddheshbmane/blueprints-skill)](https://skills.sh/siddheshbmane/blueprints-skill)

**A portable Agent Skill that turns any AI coding tool into a documentation-first, qualify-first SaaS product builder.**

Built from a real-world SaaS playbook (~8,700 lines) and distilled into a lean `SKILL.md` + deep references that work in **OpenCode, Claude Code, Codex, Grok, Gemini CLI, Cursor**, and any agent that supports the [Agent Skills](https://agentskills.io) `SKILL.md` standard.

It enforces Siddhesh's blueprint: documentation before code, intake questionnaires, multi-tenant design from day 1, no-AI-slop UI, staging-before- production deploys, browser-based user-flow E2E tests, and a mandatory task report after every change.


What it does

When you load this skill, your agent follows a proven product-development system:

  1. Ask the Project Intake questionnaire (12 topics) + Design Intake questionnaire (8 questions).
  2. Generate Phase 0 docs — SCOPE, SCHEMA, API, WIREFRAMES, ADR, BRAND (no code until you approve).
  3. Build a modular monolith → monorepo → hardening → mobile → GTM.
  4. Deploy to staging first, verify the live URL, run real-user E2E tests.
  5. Gate production behind an explicit "Ask User" gate — never auto-merges to main.
  6. Report after every task (changes, deploy, tests, brand check, known issues).

Plus an optional **product due-diligence protocol** (`references/dd.md`) to evaluate competitors, acquisitions, or your own roadmap bets.

The 15 Golden Rules

  1. Read heart.md (the full blueprint) FIRST, entirely, before anything.
  2. Ask the PROJECT INTAKE questionnaire before any work.
  3. Ask the DESIGN INTAKE questionnaire before any UI work.
  4. Generate ALL Phase 0 docs. Get user approval before coding.
  5. Multi-tenant from Day 1 — organizationId on EVERY table.
  6. No AI slop design. No purple gradients. Award-winning UI only.
  7. Ser