init-fmz
Skill0 starsChanged 2 months agoMITView on GitHub
Use /init-fmz to bootstrap a new project from a prompt: ask for the project name, create C:\faruk\<project>, write PLAN.md, install Superpowers skills, and run the Superpowers planning pipeline on the plan.
- Reads credentials
- Commits and pushes
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/automate-before-manual.mdcCursor rule
- .cursor/rules/finish-task-dev-server.mdcCursor rule
- brainstormingSkill
- caveman-commitSkill
- find-skillsSkill
- semantic-versionSkill
- systematic-debuggingSkill
- verification-before-completionSkill
- writing-plansSkill
- ask-before-architectureSkill
- automate-before-manualSkill
- caveman-commitSkill
- diagrams-mermaidSkill
- dont-be-lazySkill
- dont-forgetSkill
- find-jobSkill
- finish-with-dev-serverSkill
- google-calendar-mcpSkill
- instagram-chrome-postSkill
- project-initSkill
- recapSkill
- semantic-versionSkill
- skills-sh-maintainerSkill
- ui-change-e2eSkill
- validate-before-shareSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
42 rules. About 0 are common, 14 are distinctive, and 28 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈14
Distinctive · estimate
This author's own choices. Worth a look.
28
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 12
Use this skill only when the user explicitly invokes /init-fmz.
- Very specific: line 22
Treat all user text after /init-fmz as the project prompt (requirements, idea, or spec seed).
- Distinctive: line 23
If the prompt is empty, ask once: "Qual é o prompt ou a ideia do projeto?" and wait.
- Distinctive: line 24
Do not start scaffolding until you have a non-empty prompt.
- Distinctive: line 28
Ask once in plain chat:
- Very specific: line 39
If the slug is empty or invalid, ask again with one short example (meu-app).
- Distinctive: line 45
Run these steps in order:
- Very specific: line 47
Ensure C:\faruk exists (New-Item -ItemType Directory -Force on Windows).
- Very specific: line 49
If projectRoot already exists and is non-empty, ask whether to use it anyway or pick another name.
- Distinctive: line 50
Create the directory and init git natively:
- Very specific: line 62
Do not depend on mcp__cursor-app-control__create_project / move_agent_to_root — those exist only in Cursor.
- Very specific: line 66
Create PLAN.md at the project root with this structure:
- Distinctive: line 90
Before the first commit, also create:
- Very specific: line 117
After PLAN.md, .gitignore, and README.md exist, create the repo on GitHub and push the first commit automatically.
- Very specific: line 121
Read in order; use the first file that yields a line matching ^(ghp_|github_pat_|gho_) (classic and fine-grained PATs):
- Very specific: line 129
If none found, stop and tell the user to place a PAT in C:\faruk\secrets\github\pat.txt.
- Very specific: line 139
Default repo owner is $user (typically farukzahra).
- Distinctive: line 150
If HTTP 422 (repo already exists), reuse it — do not fail.
- Very specific: line 171
Keep the remote URL clean.
- Very specific: line 172
Do not use git push "<url-with-token>" -u origin main: with a URL as the first positional argument, origin is parsed as a refspec and the …
- Very specific: line 175
Use Conventional Commits English message.
- Very specific: line 180
Prefer Invoke-RestMethod + git on Windows.
- Very specific: line 184
If the project will deploy to a VPS (Docker, deploy-vps.sh, etc.), during or right after init scaffold:
- Distinctive: line 205
If the command fails:
- Distinctive: line 211
Do not block the pipeline on install failure if the skills are already available in the session.
- Very specific: line 215
After Superpowers, install all published skills from farukzahra/agent-skills (includes automate-before-manual, dont-be-lazy, dont-forget, …
- Very specific: line 250
Before any manual ask, agents must read automate-before-manual.
- Very specific: line 254
Read PLAN.md and run the Superpowers pipeline in this session, without asking the user to re-send the prompt.
- Very specific: line 260
REQUIRED: Read and follow brainstorming.
- Very specific: line 262
Use PLAN.md → Prompt as the starting idea.
- Very specific: line 265
Update PLAN.md Notes with any resolved constraints.
- Distinctive: line 271
Use the approved design spec (not the raw prompt alone) as input.
- Distinctive: line 277
When the user picks an execution mode:
- Very specific: line 286
Only run when /init-fmz is explicitly invoked.
- Very specific: line 287
Never depend on IDE-specific MCP tools (cursor-app-control).
- Distinctive: line 288
Always ask for the project name.
- Very specific: line 289
Always use C:\faruk\<slug> as the project root (not ~/Projects or the current workspace).
- Very specific: line 290
Always move the agent to projectRoot — or work with absolute paths — before writing files or installing skills.
- Distinctive: line 291
Never skip Superpowers brainstorming for "simple" projects.
- Very specific: line 292
Always create the GitHub repo as private and push the first commit during /init-fmz (after scaffold files).
- Very specific: line 293
Never expose or log PAT values.
- Distinctive: line 295
Keep the user informed with short status updates between phases.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Init FMZ
Use this skill only when the user explicitly invokes /init-fmz.
Bootstrap a new project under C:\faruk\<project> from the user's prompt, then hand off to the Superpowers workflow.
Works in Cursor and in VS Code Copilot — no IDE-specific MCP tools required. Use PowerShell + git for every step, always with absolute paths, because the shell working directory is not preserved between commands.
Machine layout: this skill targets one specific setup — projects in
C:\faruk\<slug>, conventions repo atC:\repo\agent-skills, secrets vault inC:\faruk\secrets/C:\repo\secrets. Adjust those roots if you clone it elsewhere.
Parse Input
- Treat all user text after
/init-fmzas the project prompt (requirements, idea, or spec seed). - If the prompt is empty, ask once: "Qual é o prompt ou a ideia do projeto?" and wait.
- Do not start scaffolding until you have a non-empty prompt.
Ask Project Name
Ask once in plain chat:
Qual o nome do projeto?
Normalize the answer into a folder-safe slug:
- lowercase
- letters, digits, and hyphens only
- spaces/underscores → hyphens
- collapse repeated hyphens
If the slug is empty or invalid, ask again with one short example (meu-app).
Confirm the final path: C:\faruk\<slug>.
Create Project
Run these steps in order:
- Ensure
C:\farukexists (New-Item -ItemType Directory -Forceon Windows). - Set
projectRoot = C:\faruk\<slug>. - If
projectRootalready exists and is non-empty, ask whether to use it anyway or pick another name. Do not overwrite without explicit confirmation. - Create the directory and init git natively:
New-Item -ItemType Directory -Force $projectRoot | Out-Null
git -C $projectRoot init -b main # git >= 2.28; else: git init, then git branch -M main
git config --global user.name; git config --global user.email # must be non-empty, else commits fail- Move the agent to the project root before any other project work. Pick the first option available:
- The agent exposes a workspace/root tool (e.g. VS Code
set_workspace) → ask the user once to confirm, then use it. - Otherwise → keep working with absolute paths:
git -C $projectRoot,npm --prefix $projectRoot, orPush-Location $projectRootinside a single command.
- The agent exposes a workspace/root tool (e.g. VS Code
Do not depend on mcp__cursor-app-control__create_project / move_agent_to_root — those exist only in Cursor. Never assume the shell starts in projectRoot: each command starts in the session directory.
Write PLAN.md
Create PLAN.md at the project root with this structure:
# Project Plan
> Created by `/init-fmz` on <YYYY-MM-DD>.
## Prompt
<verbatim user prompt — do not paraphrase>
## Goals
- [ ] Define success criteria during brainstorming
- [ ] Produce an implementation plan
- [ ] Implement and verify
## Notes
_Add constraints, stack preferences, or open questions here during Superpowers brainstorming._Scaffold Files
Before the first commit, also create:
.gitignore (minimum):
.env
.env.*
!.env.example
node_modules/
dist/
build/
.venv/
__pycache__/
*.pyc
.DS_Store
Thumbs.db
.cursor/
.agents/
.claude/README.md (one-liner from the prompt title — can expand later).
Why the agent dirs are ignored: npx skills add creates junctions on Windows (e.g. .claude/skills/<name> → .agents/skills/<name>). Git follows junctions and stages every target file as a duplicate (74 phantom files in a real run). Always run git status --short before the first commit and confirm no .agents/, .cursor/ or .claude/ paths are staged.
GitHub First Commit
After PLAN.md, .gitignore, and README.md exist, create the repo on GitHub and push the first commit automatically. Do not ask the user for a PAT before checking local secret files.
1. Resolve PAT (never print the token)
Read in order; use the first file that yields a line matching ^(ghp_|github_pat_|gho_) (classic and fine-grained PATs):
C:\faruk\secrets\github\pat.txtC:\faruk\secrets\github-pat.txtC:\faruk\secrets\pat.txtC:\repo\secrets\github\pat.txtC:\repo\faruk\.env→GITHUB_TOKEN
If none found, stop and tell the user to place a PAT in C:\faruk\secrets\github\pat.txt.
2. Detect GitHub owner
$pat = <from step 1>
$headers = @{ Authorization = "Bearer $pat"; Accept = "application/vnd.github+json"; "X-GitHub-Api-Version" = "2022-11-28" }
$user = (Invoke-RestMethod -Uri "https://api.github.com/user" -Headers $headers).loginDefault repo owner is $user (typically farukzahra). Only ask the user if they want a different owner/org.
3. Create remote repository
Always private — do not ask; never create a public repo from /init-fmz.
$body = @{ name = "<slug>"; private = $true; auto_init = $false } | ConvertTo-Json
Invoke-RestMethod -Method Post -Uri "https://api.github.com/user/repos" -Headers $headers -Body $body -ContentType "application/json"If HTTP 422 (repo already exists), reuse it — do not fail.
For an org repo: POST https://api.github.com/orgs/<org>/repos instead.
4. Commit and push
git add -A # .gitignore keeps .agents/.cursor/.claude and secrets out
git status --short # eyeball it: no secrets, no agent-dir duplicates
git commit -m "chore: initial project scaffold"
git branch -M main
git remote remove origin 2>&1 | Out-Null
git remote add origin "https://github.com/$user/<slug>.git"
# Authenticate without ever writing the token to disk:
$b64 = [Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes("x-access-token:$pat"))
git -c "http.https://github.com/.extraheader=Authorization: Basic $b64" push -u origin mainNotes:
- Keep the remote URL clean. Never
git remote add originwith credentials embedded — that writes the PAT in plain text into.git/config. - Do not use
git push "<url-with-token>" -u origin main: with a URL as the first positional argument,originis parsed as a refspec and the push fails withsrc refspec origin does not match any. The-c http.<url>.extraheaderform above keeps-u origin mainworking and sets the upstream correctly. - Set
$env:GIT_TERMINAL_PROMPT = '0'so a bad token fails fast instead of hanging on a credential prompt.
Use Conventional Commits English message. Never stage secrets (.env, pat.txt, keys).
5. Confirm
Report the repo URL https://github.com/$user/<slug> (no token in output). If push fails, read the API error and fix (auth, branch, or existing remote).
Prefer Invoke-RestMethod + git on Windows. Install gh only if already on PATH; do not block /init-fmz on gh missing.
Production secrets — GitHub Actions (mandatory for VPS deploy)
If the project will deploy to a VPS (Docker, deploy-vps.sh, etc.), during or right after init scaffold:
docs/github-secrets.md— table of every GitHub Actions secret (app + infra)..cursor/rules/production-secrets-github.mdc(Cursor) and.github/instructions/production-secrets-github.instructions.md(VS Code) — GitHub Secrets = source of truth; never commit.env; VPS.envgenerated by CI only.scripts/render-production-env.sh— writes.envfrom env vars in the deploy workflow.- Deploy workflow — step Render production .env from GitHub Secrets → SCP to VPS before
deploy-vps.sh.
Local cofre C:\repo\secrets\projects\<slug>.env is for the agent to copy values into GitHub Secrets — not for manual-only VPS .env edits.
Reference implementation: farukzahra/terapia (docs/deploy-vps.md, .github/workflows/deploy.yml).
Install Superpowers
Once the agent is at the project root, install Superpowers skills in the project. Always pass the agent targets explicitly — without -a, the CLI installs into every agent it detects on the machine and sprays junctions everywhere:
npx skills add obra/superpowers --skill "*" -a cursor github-copilot -yAgent dirs used by the skills CLI: project is .agents/skills/ for both Cursor and GitHub Copilot; global is ~/.cursor/skills (Cursor) and ~/.copilot/skills (Copilot). On this machine Copilot also resolves ~/.agents/skills.
If the command fails:
- Retry once.
- If it still fails, check whether the Superpowers skills are already available globally —
~/.agents/skills/withbrainstorming,writing-plans,systematic-debugging,verification-before-completion. In VS Code this is normal: the skill list is loaded at session start, so a mid-session project install does not appear until the window is reloaded. - Tell the user which path was used (project CLI install vs already-available global skills).
Do not block the pipeline on install failure if the skills are already available in the session.
Install Faruk agent skills (mandatory)
After Superpowers, install all published skills from farukzahra/agent-skills (includes automate-before-manual, dont-be-lazy, dont-forget, caveman-commit, etc.):
npx skills add farukzahra/agent-skills -a cursor github-copilot -y
npx skills add mattpocock/skills@handoff -a cursor github-copilot -yCopy the convention files for both agents (paths under C:\repo\agent-skills):
| From | To | Applies to |
reference\commands\{init,commit-push,recap,handoff}.md | .cursor\commands\ | Cursor |
reference\rules\automate-before-manual.mdc | .cursor\rules\ | Cursor |
.github\prompts\*.prompt.md | .github\prompts\ | VS Code Copilot |
.github\instructions\*.instructions.md | .github\instructions\ | VS Code Copilot |
$p = $projectRoot; $repo = "C:\repo\agent-skills"
New-Item -ItemType Directory -Force "$p\.cursor\rules","$p\.cursor\commands","$p\.github\instructions","$p\.github\prompts" | Out-Null
Copy-Item "$repo\reference\rules\automate-before-manual.mdc" "$p\.cursor\rules\" -Force
foreach ($c in "init","commit-push","recap","handoff") { Copy-Item "$repo\reference\commands\$c.md" "$p\.cursor\commands\" -Force }
Copy-Item "$repo\.github\instructions\*.instructions.md" "$p\.github\instructions\" -Force
Copy-Item "$repo\.github\prompts\*.prompt.md" "$p\.github\prompts\" -Forcescripts\sync-agent-conventions.ps1 -SkipSkills:$false walks only the parent of the agent-skills repo (C:\repo\*), so it does not reach a fresh C:\faruk\<slug> project. Use it to refresh existing C:\repo repos; for a new project run the copies above.
Rules + AGENTS.md
AGENTS.md is read by both Cursor and VS Code Copilot, so it holds the workflow contract for either IDE.
- Cursor rule: copy
C:\repo\agent-skills\reference\rules\automate-before-manual.mdc→.cursor/rules/. - VS Code rule: copy
C:\repo\agent-skills\.github\instructions\*.instructions.md→.github/instructions/. Copilot only reads.instructions.md(withapplyTo) there —.mdcis ignored. - Append to
AGENTS.mdthe Agent workflow (mandatory skills) table fromC:\repo\agent-skills\skills\project-init\reference\agents-snippet.mdplus the Agent automation (mandatory) block fromC:\repo\agent-skills\reference\agents-automation-snippet.md. Never replace a rich existingAGENTS.md— append or merge only.
Before any manual ask, agents must read automate-before-manual; if the user says lazy / "you do it", also dont-be-lazy.
Run Superpowers on the Plan
Read PLAN.md and run the Superpowers pipeline in this session, without asking the user to re-send the prompt.
Skills are referenced below by plain name (brainstorming, writing-plans, …). Cursor's plugin exposes the same skills namespaced as superpowers:<name> — if only that form resolves in the current IDE, use it.
Phase 1 — Brainstorming
REQUIRED: Read and follow brainstorming.
- Use
PLAN.md→ Prompt as the starting idea. - Explore context, ask clarifying questions one at a time, propose approaches, and get design approval.
- Save the approved design to
docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md. - Update
PLAN.mdNotes with any resolved constraints.
Phase 2 — Writing Plans
REQUIRED: Read and follow writing-plans.
- Use the approved design spec (not the raw prompt alone) as input.
- Save the implementation plan to
docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md. - Offer the execution choice from that skill (subagent-driven vs inline executing-plans).
Phase 3 — Continue
When the user picks an execution mode:
- Subagent-driven →
subagent-driven-development - Inline →
executing-plans
Continue until the plan is done or the user stops. Use verification-before-completion before claiming the work is finished.
Hard Rules
- Only run when
/init-fmzis explicitly invoked. - Never depend on IDE-specific MCP tools (
cursor-app-control). Every step must work withgit+ PowerShell alone, in Cursor and VS Code. - Always ask for the project name; never invent it from the prompt.
- Always use
C:\faruk\<slug>as the project root (not~/Projectsor the current workspace). - Always move the agent to
projectRoot— or work with absolute paths — before writing files or installing skills. - Never skip Superpowers brainstorming for "simple" projects.
- Always create the GitHub repo as private and push the first commit during
/init-fmz(after scaffold files). - Never expose or log PAT values; read only from
C:\faruk\secretsor documented fallbacks. - For VPS-deployed apps: production app secrets live in GitHub Actions Secrets, not in Git or manual VPS
.envalone. - Keep the user informed with short status updates between phases.
- Respond in Portuguese unless the user writes in another language.
Usage
/init-fmz Quero um app de controle financeiro pessoal com Vue e FastAPI/init-fmz(empty prompt → agent asks for the idea, then continues)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

