Instructions file CodexOpenCode
AGENTS.md instructions for tjcages/skills, covering skills monorepo — agent instructions, linear tracking (non-negotiable) and conventions.
Instructions file CodexOpenCode
AGENTS.md instructions for tjcages/skills, covering skills monorepo — agent instructions, linear tracking (non-negotiable) and conventions.
Instructions file
Claude Code instructions for tjcages/skills, covering skills monorepo — agent instructions, linear tracking (non-negotiable) and conventions.
Skill Claude CodeCodex
Make write-access AI trustworthy: every edit diffed, accept-gated, reversible, proportional, and willing to do nothing. Use when designing or auditing an agent that creates/updates/deletes user data, when adding overnight/batch AI passes, when a product’s AI writes feel silent or over-eager, or when the user asks for…
Skill Claude CodeCodex
Keep multi-platform products behaviorally one product: write platform-neutral behavior contracts per form/primitive, let each kit satisfy them natively, audit contract drift (not screenshots). Use when adding a second surface (web/iOS/macOS), when parity tickets pile up, when lightboxes/composers fork, or the user…
Skill Claude CodeCodex
Author and govern a product North Star (constitution) that every feature is judged against — premise, non-negotiables, creed, decision checklist, conflict rule. Use when starting a non-trivial product/tool, when agents disagree about what the product is, when the user asks for a manifesto / constitution / north star /…
Plugin Claude Code
Plugin marketplace listing 1 plugin: linear-methodology.
Plugin Claude Code
A proven methodology for building and tracking features, projects, and issues in Linear.
Skill Claude CodeCodex
Always-on Linear session discipline and one-time soft nudge for untracked repos. Use whenever non-trivial work is happening in a repo that already has a Linear tracking protocol in CLAUDE.md, AGENTS.md, or .cursor/rules; or when opening/working in a repo with no protocol and no .linear-tracking-skip file (ask once to…
Skill Claude CodeCodex
Finish Linear tracking pack install after skills are present: write always-on rules (Linear = default source of truth every session) and verify Linear MCP auth. Optionally offer Cursor Monitor Automation. Use when the user says "finish linear install", "finish linear-tracking install", "complete setup after skills…
Skill Claude CodeCodex
Proven methodology for building and tracking features, projects, and issues in Linear. Use when the user wants to set up Linear tracking, sync or audit a board, run a Linear health check, finish install after skills add, or keep session discipline honest. Routes to linear-setup / linear-sync / linear-monitor /…
Skill Claude CodeCodex
Health-check Linear projects for slipping dates, stale In Progress, and orphan issues. Use when the user asks for a Linear health check, atRisk scan, monitoring, /linear-monitor, or when a Cursor Automation runs the Linear tracking health recipe. Default read + comment; no mass creates. NOT for bootstrap…
Skill Claude CodeCodex
Bootstrap or extend Linear project tracking the right way — methodology, not API CRUD. Use when the user asks to set up Linear tracking, track this project in Linear, add this repo to Linear, backfill history, get ready to track, or consents after a soft-nudge from linear-discipline. Anchors to North Star, backfills…
Skill Claude CodeCodex
Sync, audit, or rescue an existing Linear project against repo reality. Use when the user asks to sync Linear, reconcile tracking, audit this project, fix a messy board, revive a parked project, or score readiness with the rubric. Runs discovery + confirmation before writes; never silent reorganize. NOT for first-time…
Skill Claude CodeCodex
Inventory-before-rewrite: map every table/endpoint/engine/UI to a destination tag, prove zero regressions, retire only when replacement is live. Use when migrating/reframing an existing product, consolidating AI engines, or the user asks for an inventory audit / lossless migration / “don’t lose anything.” NOT for…
Skill Claude CodeCodex
Owns complex multi-agent delivery as the sole root orchestrator. Use when the user says “orchestrate,” “act as the orchestrator,” “own the complete buildout,” “spin up subagents,” “manage agents until done,” or asks one root agent to own readiness, task progression, worker challenge, integration, and final delivery.…
Skill Claude CodeCodex
Write or review clear commit messages, PR titles, and PR descriptions that explain what changed and why. Use before writing git history or when asked to improve it. Not for code comments, chat replies, or docs pages.
Skill Claude CodeCodex
Give sparse, evidence-based progress updates for long-running agent tasks and projects. Use when work will take more than 15 minutes, spans multiple milestones, involves delegated agents, or when the user asks for progress bars, status cadence, fewer updates, or a global cross-agent progress rule. Not for short…