CCF Project Scaffolder
Family File Contract
Before writing, resolve the canonical output and one stable working directory per task/artifact. Reuse explicit or established task paths; otherwise use project-root
ccfa-workfiles///
, with
source/
,
assets/
,
cache/
, and
build/
only as needed. Update current files in place; do not scatter intermediates or create iteration copies. Preserve inputs and required evidence; clean only verified disposable files created by this task. Use UTF-8 text I/O and check Chinese text after saving or rendering. For file work, apply
artifact-contracts.md
and reuse the same paths across skill transitions.
Collaboration Contract
Before specialist execution, read and apply
ccf-humanization
first, then
ccf-common
. At every handoff, reuse their applicable active rules or refresh missing/changed ones. Both preflights are required even without prose; detailed editing, experiment, and maintenance modes run only when relevant.
Keep one integrating owner and actively use other skills to resolve missing prerequisites or check material findings. Reuse applicable evidence; do not skip necessary groundwork to save tokens. Before finalizing, integrate contributions and verify affected results. Follow the conditional
cooperation routes
; avoid unrelated stages and duplicate reports.
Invocation Controls
CCFA Handoff Mode: PARTIAL (Recommended).
Follow
metadata.ccf_skill_controls.handoff_question_mode
,
../ccf-common/references/handoff-modes.md
, and
../ccf-common/references/task-modes.md
. A scaffold request authorizes the necessary local structure; a dry-run or no-new-files request limits changes accordingly.
Core Rule
Create the requested project structure, template, and state without inventing research content. Preserve existing user files and complete compatible missing pieces instead of replacing an established project.
Show more
Installs
1.1K
Repository
mikubaka88/ccfa-skills
GitHub Stars
2.7K
First Seen
Jun 10, 2026
Security Audits
Gen Agent Trust Hub
Pass
Socket
Pass
Snyk
Pass