agent-starter-pack
Skill11 starsChanged 3 months agoMITView on GitHub
Use when creating a new project folder, starter pack, app scaffold, or agent-ready workspace — AGENTS.md, README, TASKS, DECISIONS, PROMPTS, an idempotent bootstrap script, and starter-pack modes.
- Reads credentials
In this repository39 other files it gives its agents.
- agent-state-machineSkill
- local-ai-ollamaSkill
- apple-hig-command-paletteSkill
- apple-hig-empty-statesSkill
- apple-hig-feedback-statusSkill
- apple-hig-inspectorsSkill
- apple-hig-macos-window-layoutSkill
- apple-hig-search-filteringSkill
- apple-hig-settingsSkill
- apple-hig-sf-symbolsSkill
- apple-hig-sidebarsSkill
- apple-hig-toolbarsSkill
- apple-hig-typographySkill
- blog-post-publishingSkill
- social-post-kitSkill
- color-principlesSkill
- kika-design-systemSkill
- emergency-switch-appSkill
- product-hunt-polish-reviewSkill
- docs-updateSkill
- project-folder-cleanupSkill
- between-runs-auditSkill
- explain-new-projectSkill
- new-project-gateSkill
- old-project-auditSkill
- project-catch-upSkill
- project-workflowSkill
- project-worth-my-timeSkill
- butterfly-effectSkill
- spreadSkill
- tilSkill
- apple-app-intentsSkill
- macos-app-distribution-dmgSkill
- macos-clipboard-pasteboardSkill
- macos-global-shortcutsSkill
- macos-launch-at-loginSkill
- macos-menubar-swiftuiSkill
- macos-notificationsSkill
- macos-permissions-privacySkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
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 12
Use this skill when creating a new project folder, starter pack, app scaffold, or agent-ready workspace.
- Distinctive: line 14
Use for project starter apps, bootstrap scripts, universal project templates, and new agent project setup.
- Distinctive: line 24
Use when the user says:
- Distinctive: line 32
create app folder structure
- Distinctive: line 38
Do not use this skill for:
- Distinctive: line 176
If creating a script:
- Distinctive: line 189
Never overwrite user files silently.
- Distinctive: line 190
Ask before copying secrets.
- Very specific: line 191
Default to .env.example, not .env.local.
≈ “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
Agent Starter Pack
Scaffold a new project so any coding agent can pick it up immediately: structure, memory, tasks, prompts, and clear instructions. Never overwrite user files or copy secrets by default.
When to use
Use this skill when creating a new project folder, starter pack, app scaffold, or agent-ready workspace.
Use for project starter apps, bootstrap scripts, universal project templates, and new agent project setup.
Core rule
Every new project should start with structure, memory, tasks, prompts, and clear instructions for the coding agent.When to use this skill
Use when the user says:
- new project starter
- create project folder
- starter pack
- bootstrap project
- AGENTS.md
- universal project template
- create app folder structure
- project scaffold
- agent-ready project
When not to use this skill
Do not use this skill for:
- Existing project refactors unless user asks to add starter files
- UI design only
- GitHub workflow only
- Full app generation without asking for target platform/framework when unknown
Default folder structure
ProjectName/
AGENTS.md
README.md
TASKS.md
DECISIONS.md
PROMPTS.md
CHANGELOG.md
.env.example
.gitignore
docs/
product-brief.md
architecture.md
ui-notes.md
prompts/
build.md
review.md
polish.md
skills/
src/
assets/
tests/Minimal project files
AGENTS.md
# AGENTS.md
## Project Goal
Describe what this project is building.
## Rules for the agent
- Read README.md first.
- Check TASKS.md before coding.
- Record major decisions in DECISIONS.md.
- Keep changes small and explain them.
- Run available tests or explain why not.
## Current Stack
- Platform:
- Language:
- Framework:
- Package manager:
## Output Requirements
After each task, report:
1. Files changed
2. What changed
3. How to test
4. Known risksREADME.md
# Project Name
## Purpose
## Features
## Setup
## Run
## Test
## NotesTASKS.md
# TASKS.md
## Now
- [ ] Define first task
## Next
- [ ] Add next task
## Later
- [ ] Add future idea
## Done
- [ ] Completed workDECISIONS.md
# DECISIONS.md
## Decision Log
### YYYY-MM-DD — Decision title
Context:
Decision:
Reason:
Tradeoffs:PROMPTS.md
# PROMPTS.md
## Build Prompt
## Review Prompt
## Polish PromptStarter pack modes
minimal = AGENTS, README, TASKS, DECISIONS, PROMPTS
app = minimal + src, assets, tests, docs
swiftui = app + Xcode notes, app architecture docs
web = app + package scripts and frontend docs
ai = app + prompts, skills, memory, evalsBootstrap script behavior
If creating a script:
Input: target folder path
Optional: include .env.local or not
Creates missing folders
Copies template files
Does not overwrite without confirmation
Prints next stepsSafe bootstrap rules
- Never overwrite user files silently.
- Ask before copying secrets.
- Default to
.env.example, not.env.local. - Print created files.
- Print skipped files.
- Make the script idempotent.
Shell script pattern
#!/usr/bin/env bash
set -euo pipefail
target="${1:-}"
if [[ -z "$target" ]]; then
echo "Usage: ./bootstrap.sh /path/to/new-project"
exit 1
fi
mkdir -p "$target"/{docs,prompts,skills,src,assets,tests}
touch "$target/README.md"
touch "$target/TASKS.md"
touch "$target/DECISIONS.md"
touch "$target/PROMPTS.md"
touch "$target/.env.example"
echo "Created project starter at: $target"Menu bar project starter app behavior
For a menu bar starter app:
Settings:
- Default projects folder
- Starter files to include
- Skill folders to include
- Default AGENTS.md template
- Git init toggle
- Open in Finder toggle
- Open in editor toggle
Create flow:
- Project name
- Location
- Starter pack mode
- Selected skills
- CreateQuality checklist
[ ] Project has AGENTS.md
[ ] Project has README.md
[ ] Project has TASKS.md
[ ] Project has DECISIONS.md
[ ] Project has PROMPTS.md
[ ] Secrets are not copied by default
[ ] Existing files are not overwritten silently
[ ] Folder structure matches project type
[ ] Next steps are printed
[ ] The agent can understand what to do nextCommon mistakes
Starting projects with only source files
No AGENTS.md
No task list
No decision log
Copying .env.local by default
Overwriting files silently
Too many folders with no purpose
No README setup instructionsPrompt template
Drop this into any coding agent (Claude Code, Codex, Cursor, …) to apply the skill:
Use the agent-starter-pack skill to create an agent-ready project starter.
Rules:
- Create a clear project folder structure.
- Include AGENTS.md, README.md, TASKS.md, DECISIONS.md, PROMPTS.md, and .env.example.
- Add docs/, prompts/, skills/, src/, assets/, and tests/ as appropriate.
- Do not overwrite existing files silently.
- Do not copy secrets by default.
- Make bootstrap scripts idempotent.
- Print created and skipped files.
- Add clear next steps for the user.
After coding:
1. List created files/folders.
2. Explain starter pack mode.
3. Explain overwrite/secrets behavior.
4. Give manual test steps.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.

