Menu

Individual skill

greenfield-project-scaffolding

0upvotes

Use only when all three gates already hold. (1) This same user turn explicitly says to start, implement, build, scaffold, or go ahead with a new project now; prior answers, planning, decisions, and reminders never authorize. (2) No named path or confirmed suitable here/current-folder target resolves placement. (3) Inspection is forbidden, or permitted top-level inspection has already proved the current root home-like, general-purpose, or falsely empty. Do not load this skill merely to check eligibility. Exclude existing work, bug fixes, component edits, server or verification work, and standalone, paste-ready, single-file, or snippet delivery.

Meta/muse-code/skills/greenfield-project-scaffolding/SKILL.md

Read pinned source

Source commit a2d33761e49b98f6ec1b48f12143264eb9b4ff4f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
71,110
Repository last updated
Nov 9, 2026
License
CC0-1.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Greenfield Project Scaffolding

Choose the project root and its normal layout before the first write.

1. Confirm current-turn authorization and a complete enough request.
   Authorization is satisfied only when the current user turn itself explicitly asks
   to start, implement, build, scaffold, or go ahead with a new project now. Answers
   to prior questions, planning or decision turns, and reminders that work remains do
   not authorize this workflow without those implementation-now words in the same
   user turn. If
   authorization is absent, stop without project-shape work or a file write. If product
   behavior or delivery constraints are missing, visibly truncated, or materially
   ambiguous, ask one focused clarification question and stop until the answer resolves
   the gap. Do not invoke this workflow merely because the deliverable is an application
Back to top