All authors
Claude Skills by dimeloper
github.com/dimeloper8 skills0 installs12 views
- Check Follow UpsScan recent daily notes' Follow-ups sections and report what's still open in the repo you are standing in — that repo's items in full, every other repo as a count, no flag and no second question — plus anything ticked as dropped or handed off, which is closed without being finished. Ends with what to do next here: a blocker to clear, work that already landed and needs confirming, the oldest item still open, and which have been open long enough to be worth re-deciding. Read-only — walks back t...Votes: 0GitHub stars: 6
- Extract Product ContextDraft a project's context/ — audience, voice, brand — from a product repo's own files rather than from memory, daily notes or store copy. Read-only. Use when writing or revising context/ for a project doc, when asked who a product is for, what it sounds like, or where it stops, or before writing anything public about a product. Writing to the vault is the update-second-brain skill's job, never this one.Votes: 0GitHub stars: 6
- Mcp Per ProjectSet up or fix per-project MCP isolation in Cursor and Claude Code, so concurrent agent sessions for different products (e.g. Acme vs Globex vs Initech) each get their own Railway, Postgres, Logfire, PostHog, etc. Use when the user mentions MCP bleed across projects, global mcp.json pollution, multiple Railway accounts/tokens on one machine, wants project-scoped MCP servers, or when onboarding a product repo (invoked from the onboard-repo skill).Votes: 0GitHub stars: 6
- Obsidian Knowledge BaseRead the Obsidian vault and score current work against it — load this repo's project context, find the practice notes that apply to this stack, cite what was followed, and name drift and gaps. Read-only. Use before large or unfamiliar changes, when the user asks what the vault says about something or about this project, or as the review half of feature complete / wrap up the feature. Writing to the vault is the update-second-brain skill's job, never this one.Votes: 0GitHub stars: 6
- Onboard RepoOnboard a Cursor repo into the hot-path/cold-path standards system: sync second-brain-workflow rules, add a thin always-apply onboarding rule, point at relevant second-brain practices, and wire project-scoped MCP (Railway / Postgres / Logfire / PostHog) — never global mcp.json. Use when the user says onboard repo, onboard this repo, set up cursor standards, sync rules into this project, or wire best practices into a new codebase. Covers quiet onboarding too — rendering into a repo you do not ...Votes: 0GitHub stars: 6
- Update Second BrainCapture the current agent session's work into the Obsidian "second brain" vault and publish it: append to today's daily note, revise the project docs the session moved, tick the follow-ups this session finished, propose and promote engineering practice notes, then commit and push. Runs from inside the working repo; the vault lives elsewhere. Use when the user says update second brain, update my second brain, capture this session, log this to second brain, second brain this, publish second bra...Votes: 0GitHub stars: 6
- Recent WorkSummarise what has actually been achieved lately, from the recent daily notes that mention this repo — built work, follow-ups that closed, practices applied — this repo first, everything else as a count. Read-only; it never ticks an item and never writes to the vault. Use when the user asks what have I done recently, what did I ship, catch me up on this repo, summarise the last week, what happened here, what's been achieved lately, or wants a standup or status update.Votes: 0GitHub stars: 6
- Unrender RepoRetire a repo from the standards system: remove the rule files a render put there, drop the local exclusion block, and forget the repo so doctor stops reporting it. Preview first, act only on --yes. Use when the user says unrender, un-onboard, retire this repo, remove the rendered rules, stop tracking this repo, take the standards out of here, or is abandoning a repo that doctor keeps naming. Not for deleting a repo — this leaves the repo intact and removes only what the engine put in it.Votes: 0GitHub stars: 6