Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From famdeck
Generate missing verification tool configs (linter, test runner, CI pipeline, coverage) to bring a project up to autonomy level L2. Use when the user says 'scaffold quality tools', 'add linting', 'set up CI', 'improve test infrastructure', or after /autonomy-assess shows the project is below L2. Shows a dry-run plan before applying.
npx claudepluginhub ivintik/private-claude-marketplace --plugin famdeckHow this skill is triggered — by the user, by Claude, or both
Slash command
/famdeck:autonomy-scaffoldThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill generates the configs a project needs to reach L2 autonomy — the level where an agent can work independently with quality gates catching mistakes. It detects the project's language (Python, TypeScript, Go, Rust) and generates idiomatic configs for that ecosystem.
Auto-detects project type and configures quality gates (lint, typecheck, test, format) for new or unfamiliar codebases. Supports Node.js, Python, Rust, and Go.
Bootstraps new projects interactively (Node/TS scripted, others manual) or adds enforcement tooling (TDD, secret scanning, file limits, git hooks, CLAUDE.md) to existing projects.
Detects your project stack and interactively configures metaswarm, writes instruction files (AGENTS.md/CLAUDE.md/GEMINI.md), coverage thresholds, and command shims for pytest, vitest, jest, go, cargo.
Share bugs, ideas, or general feedback.
This skill generates the configs a project needs to reach L2 autonomy — the level where an agent can work independently with quality gates catching mistakes. It detects the project's language (Python, TypeScript, Go, Rust) and generates idiomatic configs for that ecosystem.
Never generate configs without showing the user what will be created. The dry-run runs an assessment, identifies gaps, and shows exactly which files will be created or modified:
python -c "
from famdeck.autonomy.scaffold import scaffold_and_reassess
plan, report = scaffold_and_reassess('$PWD', dry_run=True)
if plan.is_empty:
print('No scaffolding needed -- project is fully configured.')
else:
print('Scaffolding plan:')
for f in plan.files:
print(f' CREATE {f.path} -- {f.description}')
for s in plan.pyproject_sections:
header = s.split(chr(10))[0]
print(f' APPEND to pyproject.toml: {header}')
if plan.package_json_updates:
print(f' UPDATE package.json: {list(plan.package_json_updates.keys())}')
print()
print(report.summary())
"
Present the plan and explain each item — what it does and why it's needed. Wait for the user to confirm before applying.
python -c "
from famdeck.autonomy.scaffold import scaffold_and_reassess
plan, report = scaffold_and_reassess('$PWD')
print('Scaffolding applied.')
print()
print(report.summary())
"
After applying, the reassessment shows the new autonomy level. If the project reached L2, say so. If gaps remain (e.g., the scaffolder doesn't cover every tool), explain what's still needed and suggest manual next steps.
If famdeck is not importable, scaffold manually based on what /autonomy-assess found missing. Use standard configs for the detected language — e.g., ruff.toml for Python linting, .github/workflows/ci.yml for CI, vitest.config.ts for TypeScript testing. The goal is the same: get the project to a state where tests, linting, and CI are all in place.