lordgen-full-rebuild
Skill0 starsChanged 3 months agoMITView on GitHub
Full LordGen live rebuild covering one-page progressive UX, real n8n research/approval/builder/handover orchestration, security and production QA.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- automation-builderSkill
- business-researchSkill
- competition-demoSkill
- execution-planSkill
- lordgen-3d-web-experienceSkill
- lordgen-site-upgradeSkill
- opportunity-scoreSkill
- proposal-generatorSkill
- workflow-qaSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Use progressive disclosure so each phase replaces/reveals the next state in the same work surface.
- Distinctive: line 19
Before declaring success, run code checks and a controlled end-to-end production test.
≈ “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
LordGen Full Rebuild Skill
Inspect before changing. Preserve working scaffolding. Do not create duplicate interfaces.
Implement this exact product journey: Inquiry -> Research -> Results -> Approval -> Builder -> Handover.
Use progressive disclosure so each phase replaces/reveals the next state in the same work surface.
For backend work, map the existing n8n workflows and Vercel server routes first. Reuse useful nodes. Ensure request IDs, status, retries and idempotency. Never expose credentials.
For frontend work, prioritize clarity over feature count. Keep the black/gold LordGen identity. Use restrained motion and responsive accessibility.
Before declaring success, run code checks and a controlled end-to-end production test.
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.

