
Scaffold
FreeStreamline project setup for Hyperflow.
Free · Opens the source repo
What Scaffold does
Scaffold is a tool designed to simplify the initial setup of Hyperflow in new projects. By analyzing the codebase, it builds the necessary .hyperflow/ cache and creates a memory skeleton that facilitates future interactions with AI coding agents. This skill is particularly useful for developers who want to quickly prepare their project environment without manually configuring each aspect. It automates the process of gathering project information and ensures that the environment is ready for subsequent tasks.
When you trigger Scaffold, it first checks for the existence of the .hyperflow/ directory at the project root. If it is not present, Scaffold dispatches multiple searchers to gather essential information about the project, including the technology stack, folder structure, coding conventions, dependencies, and testing setup. This information is then stored in various markdown files within the .hyperflow/ directory, which can be referenced later. If the directory already exists, Scaffold performs a staleness check to ensure that the cache remains up to date, refreshing only those files that have changed.
The skill also sets up a memory skeleton in the .hyperflow/memory/ directory, which includes files for doctrine, learnings, decisions, pitfalls, and conventions. This structured approach helps maintain a clear record of the project's evolution and decisions made throughout its lifecycle. Additionally, Scaffold can install detection shims for various AI tools, enabling seamless integration with other coding agents.
Scaffold is ideal for developers and designers who are starting new projects with Hyperflow and want to ensure that their environment is configured correctly from the outset. It removes the manual overhead of project setup and allows users to focus on development tasks instead of configuration details.
When to use it
Use Scaffold when initiating a new project with Hyperflow to automate the setup process and gather essential project data.
When not to use it
Scaffold is not suitable for mid-session changes or for projects that do not use Hyperflow, as it is specifically designed for that environment.
What you can build with it
Starting a New Hyperflow Project
When beginning a new project, use Scaffold to automatically set up the Hyperflow environment and gather necessary project details.
Refreshing an Existing Project
If your project is already set up but needs updates, run Scaffold to check for staleness and refresh the cache without starting from scratch.
Integrating AI Tools
Use Scaffold to install detection shims for AI tools, ensuring that your project can leverage additional coding agents effectively.
How to install Scaffold
View source1. Install with the skills CLI
npx skills add jeremylongshore/claude-code-plugins-plus-skills/scaffold --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by jeremylongshoreScaffold
One-shot project setup. Analyzes the codebase, builds the .hyperflow/ cache, seeds the memory skeleton, and optionally installs detection shims for other AI tools. Does not start the plan → dispatch chain — invoke /hyperflow:plan when you're ready for that.
Step 1 — Analysis Cache
Check for .hyperflow/ at project root.
If absent — dispatch parallel searchers (single message, six Agent calls):
| Label | File generated | Discovers |
|---|---|---|
Searcher — analyzing tech stack | profile.md | Name, language, framework, build commands |
Searcher — mapping folder structure | architecture.md | Dirs, patterns, routing, data flow |
Searcher — extracting conventions | conventions.md | Naming, style, linting rules |
Searcher — scanning dependencies | dependencies.md | UI lib, state, data fetching, DB, auth |
Searcher — auditing test setup | testing.md | Runner, E2E, patterns, commands |
Searcher — reading git workflow | git-workflow.md | Branches, commits, CI/CD, PR conventions |
See project-analysis.md for what each file captures.
If present — staleness check:
Compute SHA256 of tracked config files, compare against .hyperflow/.checksums. Refresh only stale files. Print Refreshing — <comma-separated list of stale files>.
After analysis:
- Write
.hyperflow/.checksums(SHA256 ofpackage.json,tsconfig.json, eslint/biome config, etc.) - Write
.hyperflow/.version(the current plugin version fromskills/hyperflow/VERSION) so the cache is stamped current. The session-start migrator (scripts/migrate-cache.py) reads this marker on later sessions and brings an older cache forward when the plugin version moves — a missing/older marker triggers an idempotent, additive migration (new memory files, refreshed doctrine copy). - Append to
.gitignoreif.hyperflow/is not already excluded
Step 2 — Memory Skeleton
Create .hyperflow/memory/ if absent:
.hyperflow/memory/
├── doctrine.md ← copied from skills/hyperflow/DOCTRINE.md
├── index.md
├── learnings.md ← empty stub (populated by /hyperflow:dispatch wrap-up)
├── decisions.md
├── pitfalls.md
├── patterns.md
├── conventions.md
├── session-context.md ← [populated by session-start hook, NOT by scaffold]
└── archive/.gitkeep
session-context.md — populated by the session-start hook, not scaffold:
Scaffold creates the empty .hyperflow/memory/ directory; it does NOT write session-context.md. That file is generated at the start of each Claude Code session by hooks/session-start, which concatenates .hyperflow/profile.md, architecture.md, and conventions.md into a single bundled file. This enables Pattern L3 (session-cached context): lean workers read one bundled file instead of three separate source files.
Limit: mid-session changes to profile.md, architecture.md, or conventions.md won't propagate to session-context.md until the next session-start. Workers can still Read the source files directly if they suspect staleness.
doctrine.md generation (idempotent):
- Source:
skills/hyperflow/DOCTRINE.md(canonical orchestration rules) - If
.hyperflow/memory/doctrine.mdis absent — copy it. - If it already exists — compare modification timestamps (or SHA256) against the source. If the source is newer, re-copy. If up-to-date, skip and print
doctrine.md — checksum match. - This enables Pattern P5 (lean worker prompts): workers
Readdoctrine on demand instead of receiving it inlined in every prompt.
learnings.md (idempotent):
- If absent — create as an empty stub with a single heading
# Learningsand the line<!-- populated by /hyperflow:dispatch wrap-up -->. - If it already exists with content — do NOT overwrite. Accumulated learnings from prior runs must be preserved across refreshes.
Other stubs — if any of decisions.md, pitfalls.md, patterns.md, conventions.md are absent, create them as an empty stub: one H1 matching the filename (title-cased) and the line <!-- to be populated by future runs -->.
Do not stub index.md. It is derived — scripts/memory-index.py writes it from the category files at every session start. A hand-written stub is overwritten on the next run.
Lean prompt note: scaffold has now populated the memory skeleton. Run /hyperflow:dispatch and workers will use skills/hyperflow/worker-prompt-lean.md by default; pass --thorough to fall back to the full inlined template.
Migration: If ~/.claude/hyperflow-memory.md exists, migrate entries matching the current project path into the appropriate memory files. Tag migrated entries [migrated].
Step 3 — Detection Shims
Offer to run scripts/setup-detection.sh --tools all to generate AGENTS.md, CLAUDE.md, and provider-specific shims.
Supported tools: claude-code (CLAUDE.md), opencode / agents / codex / cursor (AGENTS.md), antigravity (AGENTS.md + .agent/workflows/), grok (AGENTS.md + .grok/rules/hyperflow.md), all (every tool).
Flags — --tools <all|claude-code|opencode|agents|codex|cursor|antigravity|grok>, --force, --dry-run.
Default — --tools all. Ask once via AskUserQuestion if the user wants to skip any tool.
Step 4 — Summary
Print what was created, skipped, and migrated (elegant style, no icons):
Hyperflow init complete
Created .hyperflow/{profile,architecture,conventions,dependencies,testing,git-workflow}.md
Created .hyperflow/.checksums
Created .hyperflow/memory/doctrine.md — copied from skills/hyperflow/DOCTRINE.md
Created .hyperflow/memory/{index,learnings,decisions,pitfalls,patterns,conventions}.md
Created .hyperflow/memory/session-context.md — populated by hooks/session-start (not scaffold)
Skipped .gitignore entry — already present
Migrated 3 entries from ~/.claude/hyperflow-memory.md
Shims AGENTS.md, CLAUDE.md
Memory skeleton populated — workers will use lean prompts (skills/hyperflow/worker-prompt-lean.md) by default.
Pass --thorough to /hyperflow:dispatch to fall back to the full inlined template.
Hand-off
This skill does not auto-chain. Init is project setup, not feature work. When the user wants to start a feature, they invoke /hyperflow:plan.
Doctrine
Full rules in DOCTRINE.md. Output style in output-style.md.
Overview
/hyperflow:scaffold is one-shot project setup. It analyzes the codebase via 6 parallel searchers, builds the .hyperflow/ cache (profile, architecture, conventions, dependencies, testing, git-workflow), seeds the memory skeleton, and optionally writes detection shims (CLAUDE.md, AGENTS.md, Grok rules, Antigravity workflows). Does not start the plan → dispatch chain — invoke /hyperflow:plan when ready.
Prerequisites
- Git repository (recommended for tag detection + git-workflow analysis; degrades gracefully if absent).
- Write access to the project root for
.hyperflow/creation. - For migration only: existing
~/.claude/hyperflow-memory.mdfrom a prior global install.
Instructions
Numbered steps are in Step 1 — Analysis Cache through Step 4 — Summary above. Summary:
- Check for
.hyperflow/at project root; if absent, dispatch 6 parallel searchers (single message) to produce profile.md, architecture.md, conventions.md, dependencies.md, testing.md, git-workflow.md. - If present, recompute SHA256 checksums and refresh only stale files.
- Create
.hyperflow/memory/skeleton: copyskills/hyperflow/DOCTRINE.md→doctrine.md(idempotent — re-copy only if source is newer); createlearnings.mdempty stub (skip if content exists); createdecisions.md,pitfalls.md,patterns.md,conventions.mdstubs if absent.index.mdand.checksumsare derived — leave them toscripts/memory-index.py. - Migrate matching entries from legacy
~/.claude/hyperflow-memory.mdif found. - Offer
scripts/setup-detection.sh --tools allto write CLAUDE.md, AGENTS.md, and Grok/Antigravity shims when those tools are selected. - Print summary of created / skipped / migrated artifacts.
Output
See the summary block under Step 4 — Summary above. Format: plain English, em-dash separator, sections for Created / Skipped / Migrated / Shims. No icons.
Step 2 generates the following files under .hyperflow/memory/:
| File | Source | Idempotence |
|---|---|---|
doctrine.md | Copied from skills/hyperflow/DOCTRINE.md | Re-copied if source is newer; skipped if checksum matches |
learnings.md | Empty stub (# Learnings heading) | Never overwritten if content exists — preserves accumulated learnings |
decisions.md, pitfalls.md, patterns.md, conventions.md | Empty stubs | Created if absent; skipped if present |
index.md, .checksums | Derived by scripts/memory-index.py (NOT scaffold) | Scaffold does not create these; the session-start hook rebuilds them from the category files on every run. |
session-context.md | Populated by hooks/session-start (NOT scaffold) | Scaffold does not create this file; the session-start hook generates it at session open by concatenating profile.md, architecture.md, and conventions.md. Lean workers reference this bundle (Pattern L3). |
Error Handling
| Failure | Behavior |
|---|---|
| Not a git repo | Skip git-workflow.md searcher; print (skipped — no git) in summary. |
| Some searchers fail | Mark the failing files with (partial) in profile.md; continue. Other 5 sources still produce valid output. |
.hyperflow/ exists but .checksums missing | Treat all tracked configs as stale; refresh everything. |
~/.claude/hyperflow-memory.md malformed | Skip migration; print Migration skipped — legacy file parse failed at line N. Original file untouched. |
setup-detection.sh missing or non-executable | Print Detection shims skipped — scripts/setup-detection.sh not runnable. Initialization still succeeds. |
.gitignore write blocked | Print warning and the suggested line to add manually; continue. |
Examples
Fresh project
/hyperflow:scaffold
Searcher — analyzing tech stack
Searcher — mapping folder structure
Searcher — extracting conventions
Searcher — scanning dependencies
Searcher — auditing test setup
Searcher — reading git workflow
Hyperflow init complete
Created .hyperflow/{profile,architecture,conventions,dependencies,testing,git-workflow}.md
Created .hyperflow/.checksums
Created .hyperflow/memory/doctrine.md — copied from skills/hyperflow/DOCTRINE.md
Created .hyperflow/memory/{index,learnings,decisions,pitfalls,patterns,conventions}.md
Note .hyperflow/memory/session-context.md — will be populated by hooks/session-start on next session
Created .gitignore entry — .hyperflow/
Shims CLAUDE.md, AGENTS.md
Memory skeleton populated — workers will use lean prompts by default.
Refresh after dependency bump
/hyperflow:scaffold
Refreshing — dependencies.md, profile.md
Hyperflow refresh complete
Updated .hyperflow/dependencies.md, profile.md
Skipped architecture, conventions, testing, git-workflow — checksum match
Shims unchanged
Dry run
/hyperflow:scaffold --dry-run
Would create .hyperflow/profile.md (~120 lines)
Would create .hyperflow/architecture.md (~200 lines)
... (full list)
No files written.
Resources
- project-analysis.md — what each generated file captures.
- DOCTRINE.md — orchestration rules (Layer 0 project analysis).
- output-style.md — summary block formatting.
Frequently asked questions about Scaffold
Similar skills
Spring Boot Testing
Master testing techniques for Spring Boot 4 applications.
GitHub Issues
Manage GitHub issues efficiently with MCP tools.
Geofeed Tuner
Optimize your IP geolocation feeds in CSV format.
Batch Files
Master Windows batch scripting for automation and task management.
Adobe Illustrator Scripting
Automate your Illustrator workflows with ExtendScript.
Plugin Structure
Create and organize Claude Code plugins effectively.
