makieali
UserRun Claude Code as a teammate that owns work end to end. A maintained CLAUDE.md (works as AGENTS.md) plus a plan/execute/review skill pipeline with external verification, adversarial review, and structurally safe parallel execution. Dated changelog, updated when model behaviour changes.
Categories
Indexed Skills (13)
architect
Analyzes a problem and generates a phased execution plan with progress tracking, shared contracts, dependency graphs, per-phase isolation, and task-level detail. Use when tackling any large feature, refactor, migration, or complex fix. Trigger: "plan this", "break this down", "architect this", "create a plan".
clickup-connect
Connects Claude Code to a ClickUp workspace and writes its own reference notes — workspace, spaces, folders, list IDs, assignee IDs, and the API quirks it hits — so future sessions can read and update tasks without rediscovering the workspace every time. Use when wiring a task tracker into a workspace or when task IDs keep getting looked up by hand. Trigger: "connect clickup", "set up the task board", "read my tasks", "sync tasks", "what's assigned to me".
decision-log
Records durable technical decisions with their reasoning, and searches them before a settled question gets re-opened. Use when an architectural, scope, tooling or vendor choice is made or reversed, when someone asks "why is it like this", or before proposing an approach that may already have been rejected. Trigger: "log this decision", "why did we choose", "did we try", "have we decided", "record that we're not doing", "was this considered".
driver
Orchestrates the full plan-execute-review pipeline. Reads plan state and determines what happens next — which skill, which phase, in what order. Runs advisory by default, or autonomously behind explicit guardrails. Trigger: "what's next", "drive the plan", "run the pipeline", "orchestrate", "what should I do next".
executor
Implements a plan created by /architect. Reads the plan, claims a phase, works one task at a time in an isolated branch or worktree, verifies externally, commits, and records state in its own single-writer file. Designed for multi-agent parallel execution. Trigger: "execute the plan", "implement phase", "continue the plan", "work on next task", "pick up where we left off".
frontend-verify
Verifies frontend changes in a real browser — screenshots at multiple viewports, console errors, accessibility snapshot — then fixes what it finds and re-verifies. Scopes to routes touched by the current diff when no URL is given. Use after changing UI code, before shipping a frontend change, when a page "looks wrong", or when asked whether something actually works in the browser. Trigger: "check the UI", "does this look right", "screenshot the page", "verify the frontend", "review the design", "test it in the browser".
handoff
Writes a session handoff to disk before a context reset — what's done, what changed, what was decided, what was ruled out, and the single next step — then tells you whether to /clear or /compact. Use when a session is getting long or slow, before compacting, at the end of a work block, or when handing work to another person or session. Trigger: "write a handoff", "save progress", "save state", "session is getting slow", "before I compact", "wrap up", "I'm stopping here".
investigate
Deep multi-perspective codebase investigation. Use when: analyzing feasibility of a new feature, auditing code for issues, investigating bugs, evaluating technical debt, or assessing any change before planning. Dispatches investigations across the dimensions that matter for the question asked, refutes every finding before reporting it, and synthesizes into one actionable report. Trigger: "investigate this", "is this feasible", "analyze my codebase", "audit this", "what would it take to", "assess this", "can we do this", "deep dive", "research this before we start".
resume-work
Restores working context after a /clear or /compact by reading the most recent session handoff plus current git state, then reports where things stand and what the next step is. Use at the start of a session, after clearing or compacting, when picking up work from a previous day, or when taking over someone else's branch. Trigger: "resume", "pick up where we left off", "what was I doing", "restore context", "continue from the handoff", "catch me up".
reviewer
Validates work completed by /executor agents. Reviews contract compliance, test quality, edge cases, security, performance, and integration correctness in a fresh context, refutes its own findings before reporting them, and gates the verdict on recorded exit codes. Runs after a phase or the full plan is implemented. Trigger: "review phase", "validate the work", "check what was implemented", "run review", "quality check".
server-connect
Gives Claude Code non-interactive SSH access to a server and then writes a server-info folder by interrogating the machine — services, ports, deploy paths, logs, databases — rather than being told. Use when adding a dev or production server to a workspace, onboarding onto infrastructure nobody documented, or when Claude cannot reach a machine it needs. Trigger: "connect to the server", "set up ssh", "document this server", "add the dev server", "why can't you reach the box".
user-manual
Builds a print-quality PDF user manual for an application — learns the product by reading the codebase, drives the real UI with Playwright to capture screenshots, writes the prose against what was actually captured, and renders a paginated PDF with cover, table of contents, figures and callouts. Use when asked for a user manual, operator guide, onboarding handbook, client handover documentation, or training material. Trigger: "make a user manual", "write documentation for this app", "operator guide", "client handover doc", "PDF manual", "training guide".
workspace-init
Sets up a multi-repo workspace so one session can see a whole system — sibling repos plus the cross-cutting folders no single repo owns — and generates the root CLAUDE.md map by reading each repo rather than being told. Use when starting work across several related repos, onboarding onto an unfamiliar system, or when Claude keeps missing context that lives in a sibling repo. Trigger: "set up the workspace", "map this project", "I have several repos", "onboard me onto this", "create the root CLAUDE.md".
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.