All authors
Claude Skills by martinappberg
github.com/martinappberg20 skills0 installs2 views
- DevelopRun Chimaera locally and iterate on it — the daemon + Vite web-UI dev loop, ports, dev-mode auth, the build-embeds-UI gotcha, the isolated per-worktree daemon (chimaerad-isolated), and where things live. Use when starting to develop or run the app, when a change needs the real daemon/UI to see, when working in a git worktree or alongside another daemon, or when the dev server won't come up (port in use, Node version, blank UI).Votes: 0GitHub stars: 4
- Ship PrOpen a pull request for Chimaera correctly — the CI gates that must pass, the Conventional-Commit prefix that drives the automatic version bump, and the [skip release] marker for docs/chore PRs that shouldn't ship a version. Use when creating a PR, choosing a commit/PR title, or deciding whether a change should cut a release.Votes: 0GitHub stars: 4
- Audit RepoAudit Chimaera end to end for correctness, security, performance, UX, developer experience, and agent-context drift, then land bounded high-confidence fixes with proportional verification. Use for broad repository health checks or modernization passes, especially when parallel subagents are requested.Votes: 0GitHub stars: 3
- Capture Feature IntentCapture the maintainer's intent for a newly shipped user-facing feature. Use only for feat: changes; never fabricate intent.Votes: 0GitHub stars: 3
- Chat ModeWork on Chimaera's structured chat drivers, journal, server glue, or chat UI, including the live protocol verification gate.Votes: 0GitHub stars: 3
- Debug Live AppDebug a running Chimaera daemon and web UI against an isolated live preview.Votes: 0GitHub stars: 3
- DevelopRun Chimaera locally and iterate on the daemon, web UI, or native app in an isolated worktree environment.Votes: 0GitHub stars: 3
- Document FeatureAdd or update a Chimaera feature-catalog page when user-facing behavior changes.Votes: 0GitHub stars: 3
- Refresh Public MessagingRefresh Chimaera's README and public site against shipped behavior while preserving maintainer-owned positioning.Votes: 0GitHub stars: 3
- Ship PrOpen a Chimaera pull request with the correct verification, Conventional Commit prefix, and release behavior.Votes: 0GitHub stars: 3
- Verify AppVerify runtime-observable Chimaera changes end to end against the real daemon, UI, and PTY layer.Votes: 0GitHub stars: 3
- Worktree LifecycleKeep Chimaera's git worktrees and Rust target/ dirs from filling the disk: remove your worktree after your PR merges, run scripts/worktree-gc before a big build when disk is low, never touch ACTIVE worktrees.Votes: 0GitHub stars: 3
- Audit RepoAudit Chimaera end to end for correctness, security, performance, UX, developer experience, and agent-context drift, then land bounded high-confidence fixes with proportional verification. Use for broad repository health checks or modernization passes, especially when parallel subagents are requested.Votes: 0GitHub stars: 3
- Capture Feature IntentRun a short questionnaire with the human to capture WHY a newly-shipped feature exists and what about it is intentional, then write their answers into that feature's Intent section in docs/features/. Use only when a feat: ships new user-facing capability. Never for fix/refactor/chore/docs. Never fabricate intent — if the human isn't available, the page ships with Intent marked pending.Votes: 0GitHub stars: 3
- Chat ModeWork on Chimaera's structured chat mode (Tier B) — the stream-json/app-server/ACP drivers, the seq-numbered journal + gap-replay, the server glue, and the chat web UI. Use when adding or changing a chat feature, a driver, the event model, the journal/replay, the view-switch/rewind flow, or the chat UI; when a chat change needs live verification; or when deciding whether a change requires the (billed) chat-smoke suite.Votes: 0GitHub stars: 3
- Debug Live AppDebug a running Chimaera daemon + web UI against a live isolated preview — read daemon logs, the browser console, and network traffic; reproduce a failure; and recognize the common failure modes (blank UI, 401, port in use, HMR vs rebuild). Use when the app misbehaves at runtime, a change doesn't show up, the UI won't connect, or you need to see what the daemon is actually doing.Votes: 0GitHub stars: 3
- Document FeatureAdd or update a Chimaera feature page under docs/features/ so the feature catalog stays true as capabilities ship. Use when a change adds or changes user-facing behavior — a new pane surface, route, agent capability, CLI command — or when you find a feature page that's stale or missing. Defines the page structure, the derived-vs-intent split, and the rule that a feat: PR must carry its doc update.Votes: 0GitHub stars: 3
- Refresh Public MessagingRefresh Chimaera's public face — the README and the GitHub Pages site (site/index.html + site/docs.html) — so it matches what the product actually does now, and brainstorm positioning with the maintainer. Use when the README or website has drifted behind shipped features, when revisiting the selling points / tagline, or on a periodic "is our public face still current and well-said?" pass. Positioning is the maintainer's call — never rewrite it unilaterally.Votes: 0GitHub stars: 3
- Verify AppVerify a Chimaera change end-to-end against the real daemon, UI, and PTY layer before claiming it works. Use after changing daemon/server/PTY/UI behavior — especially terminal, reconnect, resize, previews, or agent-launch flows, which have all had bugs that only reproduce live. Skip for pure docs/comment changes.Votes: 0GitHub stars: 3
- Worktree LifecycleKeep Chimaera's git worktrees and their Rust build output from filling the disk — when to remove your worktree, how to run scripts/worktree-gc (dry run, --apply, --self), what the SessionStart/SessionEnd hooks do, and the hard rule never to touch an ACTIVE worktree. Use when your PR has merged, when disk space is low or a session-start hook flagged it, before a big cargo build (just check, cargo test --workspace, an app build), or when asked to clean up worktrees or target/ dirs.Votes: 0GitHub stars: 3