foundation-first

Plugin foundation-first from marketplace braynee in hamchowderr/braynee. Commands read from the repo's manifest — 5 days ago.

Skills (9)

• build-on-it

  Decide how to build on an existing project instead of from scratch, choosing the lightest option that works: use it as it is, configure it, extend it with a plugin or add-on, or fork it. Explains forking in plain words and what it costs to maintain. Use when the user says "can I change this", "shoul

• find-the-foundation

  Before building anything, find what already exists: open-source projects, official tools and platforms that already do most of the job, who maintains them, how alive they are, and what their licence allows. Use when the user says "I want to build", "I have an idea for", "how would I make", "is there

• look-under-the-hood

  Explain what a tool, platform or product is built on underneath (for example Supabase is Postgres, Coolify runs Docker, many site builders are WordPress), and what that means for testing, cost, lock-in and leaving later. Use when the user asks "what is this built on", "what's under the hood", "can I

• read-every-source

  Answer questions about a tool, SDK or platform by checking more than one source: the official docs (and their AI-readable llms.txt version), the platform's own skills, plugins and MCP servers, the source code itself, and the changelog, issues and recent pull requests. Cite where each part came from

• research-again

  Look back at something already built and check, honestly, whether an official or community project now solves it better, then compare and recommend keep, switch or combine. Use when the user says "is there a better way now", "should we still be doing this ourselves", "review what we built", or on a

• test-free-locally

  Find the free, local way to try or test a tool before paying or creating a cloud account: local stacks, emulators, test modes, sandboxes and in-browser versions (for example Supabase's local stack because it's Postgres underneath, Stripe test mode and CLI, WordPress Playground, self-hosted n8n or Co

• track-every-job

  Give every piece of work a tracked issue before it starts, link it to the change (branch, pull request, status) and close it when the change is live, so the user always knows what's done, what isn't and why anything changed. Works with Beads, GitHub Issues, Linear or any tracker the user has. Use wh

• use-the-official-library

  Before writing code that talks to an outside service (payments, email, storage, CRM, AI, auth), find and use the service's official library or SDK instead of hand-written API calls, and read its options first. Explains the difference in plain words. Use when the user asks to "connect to", "call the

• write-your-rules

  Turn how the user builds, tests and what they never want into a short rules file their AI reads at the start of every job (CLAUDE.md, AGENTS.md or the tool's equivalent), and add a line or an automatic check every time something goes wrong. Use when the user says "remember this", "don't do that agai

Similar plugins