fnl-setup
Skill4 starsChanged 14 days agoMITView on GitHub
User-run finolabs-vibecode host configuration and instruction files for Claude Code, Codex and Antigravity; add, instructions, check, scan, mode.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- finolabs/vibecodeedited, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- finolabs/vibecode★ 410% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- rules/AGENTS.mdAGENTS.md
- skills/fnl-delegate/references/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- fnl-advisorSkill
- fnl-askSkill
- fnl-coding-routerSkill
- fnl-commit-messagesSkill
- fnl-delegateSkill
- fnl-handoffSkill
- fnl-open-source-reviewSkill
- fnl-plugin-packagingSkill
- fnl-restore-pointSkill
- fnl-review-gateSkill
- fnl-security-review-gateSkill
- fnl-session-hygieneSkill
- fnl-statusSkill
- fnl-updateSkill
- fnl-verificationSkill
- fnl-versioningSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Read-back: inert facts only.
- Very specific: line 41
After core, load references/menu.md for offers (compaction included).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Set up finolabs-vibecode
Show host.md (local settings) and data root (settings/records folder) before approvals. Scopes: user account, project repository.
Command (Codex: $fnl-setup <word>) | Loads |
| none | the core path below, then the menu |
add <feature> | references/features/<feature>.md (menu below) |
instructions | references/instructions/procedure.md |
check | references/check.md (read-only), then stop |
scan / mode [args] | references/scan.md / references/mode.md |
A plain sentence selects, never answers a consent question; "install everything" grants nothing. Ambiguous: one clarifying question, core, never several features at once. Codex forwarding is unverified; use sentences. User invocation: Claude Code enforced; otherwise advisory.
Advisory (agent judgment): Talk to the user in the language they are using, including questions and option labels; keep command names, flags, file paths, skill names and other technical names unchanged. All questions: native question tool/shape in references/interview.md; headless stays open.
Core path
A bare run says: "Check: /fnl-setup check (read-only)." Show config/scan date; ask one scope question, user, project or both, recommendation first (user on a new computer, project in a repository that is not set up). Follow references/core.md.
Read-back: inert facts only; grants separate, beginner and Quick included, with no default.
Offer the beginner path: "Start with only the essential setup questions?"
Yes: Defer extras; no file changes/data sent.
No: Choose Advanced or Quick; switch later.
Undo: Switch paths; prior approvals stand.
Choices: "Yes, start with essentials" / "No, choose another path".
If yes: references/plain-language.md.
Otherwise Advanced asks each inert item; Quick confirms inert defaults once. Ask which.
In every mode these keep their own question: moving the data root and its copy; arming auto and the auto gate; filling host config; each Antigravity test-command grant; roles and review posting; the Antigravity hook write; each instruction-file write. In Quick mode unknowns stay open.
Menu
After core, load references/menu.md for offers (compaction included).
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.