⚒️ cline-foundry

Start every Cline project already configured — memory bank, rules, conventional commits, versioning, docs, and a developer role, in one commit.

The 30-second problem: every new Cline project, you re-teach the agent the same things — your coding standards (.clinerules), a memory bank, conventional commits, versioning, docs. cline-foundry encodes all of that once, so your first conversation is about the product, not the plumbing.

⚠️ Not affiliated with Cline Bot Inc. This is a community template.

Why

Cline's own docs say it best: "Ship .clinerules with your repo to teach the agent your coding standards, architecture, and deployment conventions." cline-foundry is that — plus the rest of the boring-but-correct setup — packaged as a GitHub template.

What's inside

Path	Purpose
.clinerules/	Always-on rules: role, memory bank, workflow + command vocabulary, git, versioning, docs, security, tooling.
roles/	Selectable developer-role presets (default: Staff SWE + Product Mindset).
memory-bank/	The six canonical Memory Bank files (filled in on initialize project).
docs/	Product spec, architecture, roadmap + ADR template.
.cline/skills/	Where you add reusable skills (with a sample).
.github/	Issue + PR templates for contributors.
AGENTS.md	Cross-tool pointer so this works in Cline, Claude Code, Codex, etc.
.clineignore / .gitignore	Context-reduction + secret-hygiene defaults.

Quickstart

1. Use this template (green "Use this template" button) → clone your new repo.

2. Open it in Cline and say:

   initialize project
   

3. Answer the prompts (name, description, role), then:

   follow your custom instructions
   

   …and start building.

Commands (the "CLI")

No scripts, no Makefile — you drive Cline with these trigger phrases (defined in .clinerules/02-workflow.md):

You say	Cline does
initialize project	Fill placeholders, set role, git init, first commit.
initialize memory bank	Create the six memory-bank/*.md files.
follow your custom instructions	Re-read rules + memory bank, continue where you left off.
update memory bank	Refresh all memory-bank files + commit.
git commit	Stage + conventional commit (per .clinerules/03-git.md).
version bump	Semver bump + tag + CHANGELOG.md + release notes.
sync docs	Update docs/ + memory bank in the same commit.
switch role to <name>	Swap .clinerules/00-role.md for a roles/ preset.

Roles

Pick a persona on init, or switch role to <name> anytime. Presets live in roles/:

• staff-engineer-product-mindset (default)
• principal-product-engineer
• indie-hacker-solo-founder
• security-and-infra-engineer
• frontend-product-engineer

Extending

• Add a role → drop a .md in roles/ (see CONTRIBUTING.md).
• Add a skill → create .cline/skills/<name>/SKILL.md (see .cline/skills/README.md).
• Add a rule → add a new numbered .clinerules/*.md.

Contributing

PRs welcome — see CONTRIBUTING.md. Conventional commits, minimal scope, one contribution per PR.

Author

anthowave — building AI-assisted developer tooling in public.

License

MIT © anthowave — see LICENSE.