carlitose

@carlitose source repo

35 skills
0 followers
15 hours ago last updated

▌
Project Designer · carlitose bundle
Interactive project design skill that guides users through a structured 3-phase process to produce a complete software specification document. Use when a user wants to: (1) plan a new software project from scratch, (2) design the architecture of an application, (3) create a technical specification, (4) do requirements gathering for an app or system, (5) produce a project blueprint or design doc. Triggers on phrases like "design a project", "plan an app", "create a specification", "architect a system", "help me plan a software project", "requirements gathering", "technical design", "system design document". Do NOT use for existing codebases, code reviews, debugging, or general coding tasks.

0
installs
▌
Tdd · carlitose bundle
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

0
installs
▌
Wizard · carlitose bundle
Author a staged Bash wizard for a manual setup, credential, migration, or cutover procedure that a human will run explicitly. Use when the user asks for a repeatable guided procedure with human-only actions.

0
installs
▌
Handoff · carlitose bundle
Create a small, redacted, pointer-based handoff in the operating-system temporary directory so a fresh session can continue non-ticket work. Use when the user explicitly asks for a handoff or session transfer.

0
installs
▌
To Spec · carlitose bundle
Create or update a focused feature, decision, diagnostic, architecture, or bug-analysis spec; backward compatibility is opt-in.

0
installs
▌
Diagnose · carlitose bundle
Diagnose one bug by reproducing it, testing hypotheses, locating the root cause, and returning an evidence-backed diagnosis report. Use when the user wants root-cause analysis before implementation, or when triangulate-diagnosis delegates an independent diagnostic pass.

0
installs
▌
Grill Me · carlitose
A relentless interview to sharpen a plan or design. Compatibility alias for grilling; use when the user says "grill me", wants to stress-test a plan, or asks for a design interview.

0
installs
▌
Grilling · carlitose
Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, asks for a design interview, or uses trigger phrases such as "grill me", "grill this", "stress test this plan", "poke holes", or "challenge this design".

0
installs
▌
LLM Wiki · carlitose bundle
Build and maintain a self-compiling markdown wiki — an Agent ingests raw sources and a project's own docs, compiles cross-linked concept/entity/source pages, builds a dated timeline from Git and session history, answers queries against the corpus, lints the graph for health, and applies human corrections filed in audit/. Use when (1) scaffolding a knowledge base for a research topic or a project's history, (2) ingesting articles/papers/notes into raw/sources/, (3) ingesting a repository's specs and tickets and building the temporal axis over them, (4) answering questions against the wiki and filing durable answers back, (5) running lint passes for dead links, orphan pages, index coverage, log and audit shape, (6) applying human feedback from audit/. Not for general note-taking, daily journals, or non-wiki Obsidian use.

0
installs
▌
Research · carlitose bundle
Research a factual, codebase, product, or external-documentation question using primary sources and return an evidence-backed answer. Use when the user asks to investigate, compare docs, find current behavior, answer a research ticket, or gather facts before a spec, prototype, or implementation.

0
installs
▌
Prototype · carlitose bundle
Build a throwaway prototype to answer one design, logic, data-model, state-machine, or UI question before committing to production code. Use when the user asks to prototype, sanity-check an approach, mock up a UI, explore design options, compare flows, or reduce uncertainty with disposable code.

0
installs
▌
Wait What · carlitose
Stop. That last message did not land: re-pitch it. Re-explains the previous answer in the controlled-language standard that matches the conversation language (ASD-STE100 for English, plain-language profiles for Italian and Spanish).

0
installs
▌
Wayfinder · carlitose bundle
Maintain a persistent map and investigation frontier for huge or vague work, using canonical normalized tickets and opt-in compatibility.

0
installs
▌
Ask Skills · carlitose bundle
Route a request to the smallest composable local skill flow without duplicating orchestration or removed super-autopilot behavior.

0
installs
▌
Explain Pr · carlitose bundle
Render and optionally publish a deterministic PR body from a validated verification bundle without changing its claims.

0
installs
▌
To Tickets · carlitose bundle
Break a spec into independently-grabbable tracer-bullet tickets and emit each versioned Ticket Envelope through the canonical scheduler contract.

0
installs
▌
Code Review · carlitose bundle
Review a runner candidate or standalone PR, commit, local diff, or requested scope read-only for regressions, evidence gaps, and overclaims.

0
installs
▌
QA Test Plan · carlitose bundle
Plan causal QA for a runner candidate or standalone PR, commit, local diff, or requested scope without executing or deciding release.

0
installs
▌
Execute Ticket · carlitose bundle
Implement one normalized ticket through a bounded quality loop and return a validated handoff without scheduler or Git finalization side effects.

0
installs
▌
Codebase Design · carlitose bundle
Shared vocabulary for designing deep, testable modules and evaluating interfaces, implementations, seams, adapters, leverage, and locality. Use when shaping a module boundary, comparing interface designs, classifying dependencies, or deciding where a test seam belongs.

0
installs
▌
Domain Modeling · carlitose
Build and sharpen a project's domain model and ubiquitous language while planning or changing software. Use when the user wants glossary work, bounded-context language, domain terminology cleanup, ADR-worthy decisions, or docs that keep product language aligned with code.

0
installs
▌
Grill With Docs · carlitose
A relentless interview to sharpen a plan or design, while also creating or updating domain-modeling docs such as CONTEXT.md glossary entries and sparse ADRs when justified.

0
installs
▌
Peer Programming · carlitose
Use this skill whenever the user wants to peer program, pair program, or do collaborative coding where THE HUMAN writes the code and Claude only assists. Trigger on phrases like "pair program", "peer program", "let's code together", "I'll write you review", "drive me through this", "I want to be the driver", "you navigate I type", "teach me by letting me write it", or any workflow where the human is the typist and Claude is the navigator/reviewer. Also trigger when the user wants to learn by writing code themselves with Claude's guidance, or explicitly says Claude should NOT write the implementation. Use this even if the user doesn't say "skill" — the inversion of the usual write/review roles is the signal.

0
installs
▌
Ticket Autopilot · carlitose bundle
Drive a ticket folder AFK through deterministic scheduling, isolated implementation, evidence-backed quality gates, provider-neutral PRs, and explicit merge authorization.

0
installs
▌
To Questionnaire · carlitose bundle
Draft a focused questionnaire for an explicit external decision owner when the current user cannot answer alone. Use only when the user asks to externalize questions; never send the draft.

0
installs
▌
Codebase Improver · carlitose bundle
End-to-end, self-contained Python/TypeScript workflow that maps and audits a whole repo, then recursively deepens modules. Use to improve or modernize a codebase, reduce technical debt, make this more testable, find refactoring opportunities, deepen shallow modules, consolidate tightly-coupled modules, make codebase AI-navigable, or run a full-repo audit. Worker delegation is optional and human-gated.

0
installs
▌
Project Blueprint · carlitose bundle
Discover the architectural slices, conventions, and patterns of a codebase by examining its structure, then output a written BLUEPRINT.md per project under docs/architecture (plus a SYSTEM_MAP.md for monorepos) that captures what the project actually does. Discovery means finding repeated structural patterns (slices) from folder shapes and naming conventions, not applying architectural theory. Detects monorepos with sub-projects, internal dimensions like voice/text verticals, and slice variants. Human-in-the-loop by design — pauses to ask about singletons vs templates, canonical reference selection, slice naming, and pre-write confirmation. Use whenever the user wants to map a codebase, onboard onto a project, document architecture, understand "how does this team add X", build a slice catalog, or generate a reference document for new contributors.

0
installs
▌
Verification Audit · carlitose bundle
Produce, validate, and reduce the canonical Verification Record for a frozen candidate without fabricating evidence or authorization.

0
installs
▌
Writing For Agents · carlitose bundle
Improve documents that agents consume, including skills, AGENTS.md, CLAUDE.md, prompts, and linked instructions. Use when creating or editing agent-facing guidance whose triggers, hierarchy, completion criteria, or wording need to be clearer.

0
installs
▌
Code Simplification · carlitose bundle
Simplify the current candidate diff for clarity while preserving behavior, scope, tests, errors, side effects, and project conventions.

0
installs
▌
Change Status Ticket · carlitose
Change an exact ticket's administrative disposition to open, on-hold, or canceled. Use only for explicit hold, cancel, reopen, or disposition-setting requests; not for implementing, completing, pausing, blocking, stopping, waiting on, or inspecting a ticket.

0
installs
▌
Pr Antipattern Review · carlitose bundle
Review a diff (pull request, commit, or local changes) by comparing it against the project's BLUEPRINT.md slice catalog. Auto-detects the input format (git diff, GitHub/GitLab PR URL or number, commit SHA, pasted diff). Loads the blueprint for each project the diff touches and classifies findings as deviations from declared slices, universal anti-patterns, or improvements. Human-in-the-loop on ambiguity (slice classification, severity, ambiguous deviations). Output is ephemeral — emitted to chat or saved on request, never auto-committed. Use whenever the user asks "review this PR", "check my changes", "any anti-patterns in this commit", "is this safe to merge", "look at PR

0
installs
▌
Triangulate Diagnosis · carlitose bundle
Cross-check a hard bug with independent diagnostic workers only when the user explicitly requests them; otherwise run one inline diagnosis. Use when a bug is high-stakes, has resisted a single diagnosis pass, or when the user wants to triangulate or cross-check before committing to a fix.

0
installs
▌
Resolving Merge Conflicts · carlitose bundle
Trace both sides of an in-progress Git merge or rebase conflict, resolve compatible intent with scoped authority, and gate incompatible intent. Use only when the user explicitly asks to inspect or resolve current conflicts.

0
installs
▌
Improve Codebase Architecture · carlitose bundle
Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.

0
installs

35 published skills