oss-project-scaffold
Skill0 starsChanged 27 days agoMITView on GitHub
Scaffold a new OSS CLI project with package.json, tsconfig, README template, Vitest, CI, and LICENSE. The standardized starting point for all Energy OSS tools.
- Installs packages
4 other projects use a version of this.
Adopted by
Most recently taken up by
- naman10parikh/pennyword for word, first seen Nov 8, 2026
- naman10parikh/wikimemword for word, first seen Nov 8, 2026
- naman10parikh/turboword for word, first seen Oct 25, 2026
- naman10parikh/agentgridword for word, first seen Oct 20, 2026
Other versions4 projects use a version of this.
Word for word · 4
- naman10parikh/agentgrid★ 9100% same
- naman10parikh/wikimem★ 8100% same
- naman10parikh/penny★ 0100% same
- naman10parikh/turbo★ 0100% same
Edited · 0
None found.
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 repository59 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- agent-runtimeSkill
- frontend-designSkill
- architectSkill
- deep-thinkSkill
- design-systemsSkill
- ecosystem-referenceSkill
- fractal-delegationSkill
- harness-reviewSkill
- heartbeatSkill
- integrate-resourcesSkill
- llm-council-critiqueSkill
- loop-createSkill
- mcp-setupSkill
- memory-compressionSkill
- memorySkill
- model-routingSkill
- playwright-cliSkill
- repo-scoutSkill
- self-improveSkill
- skill-creatorSkill
- skill-routingSkill
- sprintSkill
- test-visualSkill
- troubleshootSkill
- ux-auditSkill
- Accessibility AuditorSkill
- artifacts-builderSkill
- brand-guidelinesSkill
- canvas-designSkill
- frontend-patternsSkill
- design-mirrorSkill
- design-system-starterSkill
- design-to-codeSkill
- feature-design-assistantSkill
- figma-implement-designSkill
- frontend-designSkill
- frontend-dev-guidelinesSkill
- mobile-designSkill
- motion-canvasSkill
- pixel-agent-uiSkill
- pixel-animateSkill
- pixel-anti-slopSkill
- pixel-brain-pageSkill
- pixel-migrate-next16Skill
- pixel-rsc-boundarySkill
- pixel-ship-gateSkill
- premium-web-designSkill
- senior-frontendSkill
- shadcnSkill
- tailwind-design-systemSkill
- tailwind-patternsSkill
- theme-factorySkill
- ui-design-systemSkill
- ui-ux-pro-maxSkill
- ux-researcher-designerSkill
- web-design-guidelinesSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
When creating a new CLI tool in tools/ or oss-projects/
- Distinctive: line 9
When META-FORGE or any company spawns a builder for a new OSS project
- Distinctive: line 10
When starting any TypeScript CLI that will be published to npm
- Very specific: line 126
Follow the shared conventions in .claude/contracts/shared.md:
- Distinctive: line 150
All boilerplate handled — builder can focus on core logic
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
When to Use
- When creating a new CLI tool in
tools/oross-projects/ - When META-FORGE or any company spawns a builder for a new OSS project
- When starting any TypeScript CLI that will be published to npm
Process
Step 1: Create Directory Structure
{project-name}/
├── src/
│ ├── index.ts # CLI entry point (commander.js)
│ ├── types.ts # Type definitions
│ └── utils.ts # Shared utilities
├── tests/
│ └── index.test.ts # Vitest tests
├── bin/
│ └── {project-name}.js # Compiled CLI entry (shimmed by build)
├── package.json
├── tsconfig.json
├── vitest.config.ts
├── README.md
├── LICENSE
├── .npmignore
└── .gitignoreStep 2: Package.json Template
{
"name": "{project-name}",
"version": "1.0.0",
"description": "{one-liner}",
"bin": {
"{project-name}": "./dist/index.js"
},
"main": "./dist/index.js",
"types": "./dist/index.d.ts",
"files": ["dist/", "README.md", "LICENSE"],
"scripts": {
"build": "tsc",
"dev": "tsc --watch",
"test": "vitest run",
"test:watch": "vitest",
"prepublishOnly": "pnpm build && pnpm test"
},
"license": "MIT",
"engines": { "node": ">=18" },
"keywords": ["ai", "claude", "agent", "{category}"],
"author": "Naman Parikh",
"repository": {
"type": "git",
"url": "https://github.com/naman10parikh/{project-name}"
}
}Step 3: Dependencies (Common Stack)
pnpm add commander chalk # CLI essentials
pnpm add -D typescript vitest @types/node # Dev toolsOptional (add only if needed):
ora— spinnerscli-table3— table outputboxen— boxed outputinquirer— interactive promptsblessedorink— full TUI dashboard
Step 4: TSConfig Template
{
"compilerOptions": {
"target": "ES2022",
"module": "NodeNext",
"moduleResolution": "NodeNext",
"outDir": "./dist",
"rootDir": "./src",
"strict": true,
"declaration": true,
"esModuleInterop": true,
"skipLibCheck": true,
"forceConsistentCasingInFileNames": true
},
"include": ["src/**/*"],
"exclude": ["node_modules", "dist", "tests"]
}Step 5: CLI Entry Point Pattern
#!/usr/bin/env node
import { Command } from "commander";
import chalk from "chalk";
const program = new Command();
program.name("{project-name}").description("{description}").version("1.0.0");
program
.command("run")
.description("Primary command")
.action(async () => {
// Implementation
});
program.parse();Step 6: README Template
Follow the shared conventions in .claude/contracts/shared.md:
- Title + one-liner
- Badges (MIT, npm, TypeScript, CI)
- Demo output / GIF placeholder
- Install (
npx {name}ornpm install -g {name}) - Usage (all commands with examples)
- How it works
- Configuration
- Contributing
- License
- "See Also" — link to 2-3 related Energy tools
Step 7: Verification
pnpm install && pnpm build && pnpm test
node dist/index.js --help
npm pack --dry-runOutput
- Complete project scaffold ready for implementation
- All boilerplate handled — builder can focus on core logic
- Passes npm-publish-checklist from day one
Model Tier
- Haiku for file generation (steps 1-5)
- Sonnet for README writing (step 6)
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.

