oliver-kriska
- 177 skills
- 0 followers
- last month last updated
- ▌ Phx Help 4 · oliver-kriska bundleChoose Phoenix review, plan, debug, or test command. Use when user asks which phx-* command or plugin skill handles a task; do not route only to a domain skill. NEVER for bare /help; NOT for ambiguous requests (use intent-detection) or a plugin tour.
- ▌ Phx Init 4 · oliver-kriska bundleInitialize plugin in a project — install Iron Laws, auto-activation rules, and reference auto-loading into CLAUDE.md. Use when setting up or updating the plugin.
- ▌ Phx Perf 4 · oliver-kriska bundleAnalyze Elixir/Phoenix performance — N+1 queries, assign bloat, ecto optimization, genserver bottlenecks. Use when slowness, timeouts, or high memory reported.
- ▌ Phx Work 4 · oliver-kriska bundleExecute Elixir/Phoenix plan tasks with progress tracking. Use after phx-plan to implement features with mix compile and mix test verification after each step, or --continue to resume interrupted work.
- ▌ Phx Intro 2 · oliver-kriska bundleWalk through the Elixir/Phoenix plugin commands, workflow, and features in 6 interactive sections. Use when a new user wants to learn what the plugin offers or needs a refresher on available commands.
- ▌ Phx Audit 3 · oliver-kriska bundleProject health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
- ▌ Phx Brief 2 · oliver-kriska bundleInteractive briefing of a plan file — explains reasoning, schema decisions, component choices. Use when developers need to understand a plan before approving.
- ▌ Phx Triage 3 · oliver-kriska bundleTriage review findings interactively — approve, skip, or prioritize each issue. Use after /skill:phx-review to filter findings before fixing.
- ▌ Testing 3 · oliver-kriska bundleWrite or repair Elixir tests with ExUnit, sandbox isolation, async reliability, Mox, ExMachina, and LiveViewTest. Use for test files, test setup, or failing/flaky tests. NOT for investigating an application bug outside the test suite.
- ▌ Phx Full 3 · oliver-kriska bundleRun a portable sequential plan-work-verify-review-compound lifecycle. Use optional generic workers only when Amp makes them available.
- ▌ Phoenix Contexts 2 · oliver-kriska bundlePhoenix context design — creating/splitting contexts, Scope (1.8+), Ecto.Multi, PubSub, routers, plugs, controllers. Use when editing contexts, routers, or designing boundaries.
- ▌ Liveview Patterns 2 · oliver-kriska bundleBuild LiveView: async data (assign_async), PubSub (check connected?), phx-change events, form components/modals/uploads, streams for lists, live_patch. Use when handling interactions, debugging events, or tracking Presence.
- ▌ Phx Review 2 · oliver-kriska bundleReview changed Elixir/Phoenix code read-only. Check requirements, cite evidence, deduplicate findings, and return a severity-based verdict.
- ▌ Watch Pr 2 · oliver-kriska bundleWatch an Elixir/Phoenix PR with an Amp Orb keep-alive lease until required non-deployment CI is green and review threads are resolved. Use after opening or updating a PR.
- ▌ Intent Detection 4 · oliver-kriskaRoute ambiguous or mixed Phoenix/LiveView/Ecto requests before choosing a workflow. Use when user is unsure where to start/how to approach work, asks for the right workflow, or combines intents such as fixing and refactoring. NOT for a clear task.
- ▌ Deploy 2 · oliver-kriska bundleElixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.
- ▌ Phx Investigate 3 · oliver-kriska bundleInvestigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence; Codex subagents are optional.
- ▌ Narrow Bare Rescue 3 · oliver-kriska bundleNarrow bare rescue in Elixir so real errors like KeyError and typos propagate instead of being swallowed. Use to audit rescues and refactor error handling.
- ▌ Phx Learn From Fix 3 · oliver-kriska bundleCapture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
- ▌ Security 2 · oliver-kriska bundleEnforce Elixir/Phoenix security — auth, OAuth, sessions, CSRF, XSS, SQL injection, input validation, secrets. Use when editing auth files, login flows, RBAC, or API keys.
- ▌ Ecto Constraint Debug 3 · oliver-kriska bundleDebug Ecto constraint violations - trace triggers, check migrations, find duplicate data. Use when seeing unique_constraint, foreign_key_constraint, or check_constraint errors.
- ▌ Ecto Patterns 2 · oliver-kriska bundleEcto patterns — schemas, changesets, queries, migrations, Multi, associations, preloads, upserts. Use when editing Repo calls, Ecto.Query, or schema fields. Skip for Ash.
- ▌ Hexdocs Fetcher 2 · oliver-kriskaFetch HexDocs for Elixir libraries with HTML-to-markdown conversion. Use when looking up docs on hexdocs.pm — modules, functions, guides, changelogs.
- ▌ Phx Brainstorm 2 · oliver-kriska bundleBrainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
- ▌ Phx Boundaries 2 · oliver-kriska bundleAnalyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.
- ▌ Phx Codex Loop 2 · oliver-kriska bundleFix Elixir/Phoenix code until Codex CLI review comes back clean — bounded review, fix, verify loop before opening a PR. Use when codex is installed and you want an external cross-model critic on your changes before pushing.
- ▌ Phx Deps Audit 2 · oliver-kriska bundleAudit Hex deps for supply-chain security risk — bidi chars, compile-time exec, maintainer changes, typosquats, CVEs. Use after mix deps.update, when checking if a package upgrade is safe, or reviewing mix.lock PR diffs.
- ▌ Oban 2 · oliver-kriska bundleOban job processing — workers, perform/1 (OSS) and process/1 (Pro), queues, cron, retries, unique jobs, idempotency, Oban Pro (Workflow, Batch, Chunk, Smart Engine), Testing. Use when writing Oban workers, queue config, or debugging jobs.
- ▌ Phx Deps Update 2 · oliver-kriska bundleBump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (phx-investigate).
- ▌ Phx Freeze 3 · oliver-kriskaApply an advisory edit scope in this session. Use for read-only or directory-scoped work; no enforcement hook is installed.
- ▌ Phx Recall 2 · oliver-kriska bundleRecall prior work from past sessions — how a bug was fixed, what was decided, where a pattern lives. Use when asked 'have we done this before' or 'how did I fix X' in Elixir/Phoenix work. ccrider MCP when available, else git + solution docs.
- ▌ Phx Plan 2 · oliver-kriska bundlePlan features spanning multiple domains: billing (Stripe), auth; Use when designing interconnected systems…
- ▌ Phx Deps Vet 2 · oliver-kriska bundleRecord a vetted Hex package version in hex_vet.exs after a security review — manages the audit ledger, not the scanner. Use to approve a dep after phx-deps-audit findings or to initialize hex_vet.exs.
- ▌ Phx Document 4 · oliver-kriska bundleGenerate @moduledoc/@doc for tested Elixir features; may update their README section or ADR. Not for docs lookup, documentation audits/reviews, or capturing standalone decisions.
- ▌ Phx Examples 4 · oliver-kriskaProvide Phoenix, LiveView, Ecto, OTP, or Oban examples. Use when asked for sample code, a walkthrough, a proper implementation, or expected workflow output. Pair with domain skills. NOT for debugging, direct changes, best-practice advice, or audits.
- ▌ Ash Framework 2 · oliver-kriskaAsh Framework — resources, actions, policies, aggregates, calculations, AshPhoenix.Form, LiveView, migrations. Use when generating resources via mix ash.codegen, editing changes, checks, types, validations, or domain code interfaces.
- ▌ Compound Docs 5 · oliver-kriska bundleSearchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.
- ▌ Ecto N1 Check 2 · oliver-kriska bundleDetect N+1 query anti-patterns specifically — Repo calls inside Enum/for loops, missing preloads on associations. Use when N+1 is explicitly suspected, NOT for unrelated Ecto questions or wider database performance.
- ▌ Elixir Idioms 3 · oliver-kriska bundleOTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
- ▌ Phx Challenge 2 · oliver-kriskaChallenge mode reviews - rigorous questioning before approving changes. Use when you want thorough scrutiny of Ecto changes, LiveView events, OTP designs, or PR readiness.
- ▌ Phx Pr Review 3 · oliver-kriska bundleAddress feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
- ▌ Ecto Constraint Debug 2 · oliver-kriska bundleDebug Ecto constraint violations - trace triggers, check migrations, find duplicate data. Use when seeing unique_constraint, foreign_key_constraint, or check_constraint errors.
- ▌ Tidewave Integration 4 · oliver-kriska bundleTidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
- ▌ Narrow Bare Rescue 2 · oliver-kriska bundleNarrow bare rescue in Elixir so real errors like KeyError and typos propagate instead of being swallowed. Use to audit rescues and refactor error handling.
- ▌ Intent Detection 3 · oliver-kriskaRoute ambiguous or mixed Phoenix/LiveView/Ecto requests before choosing a workflow. Use when user is unsure where to start/how to approach work, asks for the right workflow, or combines intents such as fixing and refactoring. NOT for a clear task.
- ▌ Elixir Idioms 2 · oliver-kriska bundleOTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
- ▌ Compound Docs 4 · oliver-kriska bundleSearchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.
- ▌ Tidewave Integration 3 · oliver-kriska bundleTidewave MCP runtime tools — debugging, smoke testing, live state; Use when evaluating code in a running Phoenix app.
- ▌ Phx Mix Compression 4 · oliver-kriska bundleReduce mix output noise (5-15% token savings) by installing rtk; Use when long mix output floods context.
- ▌ Phx Learn From Fix 2 · oliver-kriska bundleCapture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning…
- ▌ Phx Investigate 2 · oliver-kriska bundleInvestigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence, and use optional native OpenCode subagents only when useful.
- ▌ Phx Mix Compression 3 · oliver-kriska bundleReduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.
- ▌ Testing 2 · oliver-kriska bundleWrite or repair Elixir tests with ExUnit, sandbox isolation, async reliability, Mox, ExMachina, and LiveViewTest. Use for test files, test setup, or failing/flaky tests. NOT for investigating an application bug outside the test suite.
- ▌ Intent Detection 2 · oliver-kriskaRoute ambiguous or mixed Phoenix/LiveView/Ecto requests; Use when user is unsure where to start/how to approach work…
- ▌ Constraint Debug · oliver-kriskaCompatibility alias for the Elixir/Phoenix plugin's Ecto constraint debugger. Invoke explicitly with /ecto:constraint-debug.
- ▌ Phx Help 2 · oliver-kriska bundleChoose Phoenix review, plan, debug, or test command. Use when user asks which /phx-* command or plugin skill handles a task; do not route only to a domain skill. NEVER for bare /help; NOT for ambiguous requests (use intent-detection) or a plugin tour.
- ▌ Phx Init 2 · oliver-kriska bundleInitialize plugin in a project — install Iron Laws, auto-activation rules, and reference auto-loading into CLAUDE.md. Use when setting up or updating the plugin.
- ▌ Phx Perf 2 · oliver-kriska bundleAnalyze Elixir/Phoenix performance — N+1 queries, assign bloat, ecto optimization, genserver bottlenecks. Use when slowness, timeouts, or high memory reported.
- ▌ Phx Work 2 · oliver-kriska bundleExecute Elixir/Phoenix plan tasks with progress tracking. Use after /phx-plan to implement features with mix compile and mix test verification after each step, or --continue to resume interrupted work.
- ▌ Phx Quick · oliver-kriskaImplement small Phoenix changes without planning — add validations, update routes, fix components, create migrations. Use for single-file edits under 50 lines.
- ▌ Phx Full 2 · oliver-kriska bundleRun portable end-to-end lifecycle with gates. Use for full features; use $elixir-phoenix:phx-work for an existing plan.
- ▌ Phx Help 3 · oliver-kriska bundleRecommend the right $elixir-phoenix:phx-* workflow. Use when choosing a plugin skill, not for Codex /help.
- ▌ Phx Init 3 · oliver-kriska bundleInitialize plugin in a project — install Iron Laws, auto-activation; Use when setting up or updating the plugin.
- ▌ Phx Perf 3 · oliver-kriska bundleAnalyze Elixir/Phoenix performance — N+1 queries, assign bloat, ecto; Use when slowness, timeouts, or high memory…
- ▌ Phx Work 3 · oliver-kriska bundleExecute Elixir/Phoenix plan tasks with progress tracking. Use after $elixir-phoenix:phx-plan to implement features…
- ▌ Phx Triage 2 · oliver-kriska bundleTriage review findings interactively — approve, skip, or prioritize each issue. Use after /phx-review to filter findings before fixing.
- ▌ Phx Audit 2 · oliver-kriska bundleProject health audit and health check — architecture, performance; Use when assessing overall project health…
- ▌ Phx Compound 3 · oliver-kriska bundleCapture solved problems as searchable solution docs. Use after fixing bugs, when "that worked", or after successful /skill:phx-review or /skill:phx-investigate.
- ▌ Phx Techdebt 3 · oliver-kriskaAnalyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues. Use when asked about code quality, cleanup, or what to improve.
- ▌ Phx Freeze 2 · oliver-kriskaApply an advisory scope in this session. Use for read-only or directory-scoped work; no enforcement hook is installed.
- ▌ Phx Document 2 · oliver-kriska bundleGenerate @moduledoc/@doc for tested Elixir features; may update their README section or ADR. Not for docs lookup, documentation audits/reviews, or capturing standalone decisions.
- ▌ Phx Examples 2 · oliver-kriskaProvide Phoenix, LiveView, Ecto, OTP, or Oban examples. Use when asked for sample code, a walkthrough, a proper implementation, or expected workflow output. Pair with domain skills. NOT for debugging, direct changes, best-practice advice, or audits.
- ▌ Compound Docs 2 · oliver-kriska bundleSearchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.
- ▌ Compound Docs 3 · oliver-kriska bundleSearchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.
- ▌ Phx Compound 4 · oliver-kriska bundleCapture solved problems as searchable solution docs. Use after fixing bugs, when "that worked", or after successful…
- ▌ Phx Document 3 · oliver-kriska bundleDocument tested Elixir APIs; may update README/ADRs. Not for docs lookup, audits/reviews, or standalone decisions.
- ▌ Phx Examples 3 · oliver-kriskaProvide Phoenix, LiveView, Ecto, OTP, or Oban examples. Use when asked for sample code, a walkthrough, a proper…
- ▌ Phx Techdebt 4 · oliver-kriskaAnalyze Elixir/Phoenix technical debt — duplicates, refactoring; Use when asked about code quality, cleanup, or what…
- ▌ Phx Watch Pr 3 · oliver-kriska bundleWatch an Elixir/Phoenix PR for new review comments (bot + human); Use after opening a PR or pushing, while waiting on…
- ▌ Phx Pr Review 2 · oliver-kriska bundleAddress feedback left on a GitHub pull request: fetch unresolved; Use for a PR URL/number or reviewer comments.…
- ▌ Phx Compound 2 · oliver-kriska bundleCapture solved problems as searchable solution docs. Use after fixing bugs, when "that worked", or after successful /phx-review or /phx-investigate.
- ▌ Phx Techdebt 2 · oliver-kriskaAnalyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues. Use when asked about code quality, cleanup, or what to improve.
- ▌ Phx Watch Pr 2 · oliver-kriska bundleWatch an Elixir/Phoenix PR for new review comments (bot + human) and CI results via a background watcher that wakes Claude only on real events. Use after opening a PR or pushing, while waiting on CI or reviewers.
- ▌ Tidewave Integration 2 · oliver-kriska bundleTidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
- ▌ Phx Mix Compression 2 · oliver-kriska bundleReduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.
- ▌ Scribe Kb · oliver-kriska bundleRead, write, and search a scribe-managed knowledge base (markdown vault with frontmatter conventions, wikilinks, and qmd hybrid search). Use when the user's project has a scribe.yaml (KB root) or a .claude/<kb_name>/ drop-file directory (consumer side), or when they mention scribe, scriptorium, qmd, drop files, or "my KB". Covers frontmatter schema, wikilink syntax, drop-file pattern, search via qmd, and directory taxonomy.
- ▌ Scribe CLI · oliver-kriska bundleSet up and operate the scribe CLI — install/init personal or team KBs, diagnose with doctor/status, run sync/extraction, manage cron and Full Disk Access, and pick the right command for a maintenance goal. Use when the user wants to install or run scribe, asks which scribe command or init/team flags to use, says their KB is stale/empty or extraction/sync stopped, or is reading `scribe doctor`/`scribe status` output. For authoring KB content use scribe-kb; for the `scribe lint` content-quality queue use scribe-kb-tidy.
- ▌ Scribe Kb Tidy · oliver-kriska bundleClean up a scribe knowledge base — split bloated articles, expand or merge thin stubs, archive overgrown rolling files, and merge KB-self-named directories. Use when `scribe lint` reports content-quality warnings (bloated article, thin article, rolling file overgrown, directory named after the KB), or when the user asks to tidy, prune, split, archive, or de-clutter their KB / scriptorium.
- ▌ Getscribe Site Sync · oliver-kriska bundleAudit and re-deploy the getscribe.dev marketing site whenever scribe ships a new release. Use this whenever a new scribe version is tagged or pushed, a new CHANGELOG entry lands, or the user says anything like "sync the site", "update getscribe.dev", "the site is stale", "check the site against the changelog", "did the landing page get updated for this release", or after running `git tag v*`. Also use it proactively when you notice the latest git tag / top CHANGELOG entry is newer than what the site copy reflects. The site is deliberately VERSION-FREE — this skill keeps it factually current with the CHANGELOG while enforcing that no version string ever leaks onto any surface, then deploys to Cloudflare and verifies the live result.
- ▌ Deps Update · oliver-kriska bundleBump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (/phx:investigate).
- ▌ Investigate · oliver-kriska bundleInvestigate bugs and errors in Elixir/Phoenix — root-cause analysis for crashes, exceptions, stack traces, test failures. Use --parallel for deep 4-track investigation.
- ▌ Permissions · oliver-kriska bundleRecommend safe Bash permissions for Elixir mix commands in settings.json. Use when permission prompts slow workflow, "fix permissions", "reduce prompts", "auto-allow mix".
- ▌ Ecto Constraint Debug · oliver-kriska bundleDebug Ecto constraint violations - trace triggers, check migrations; Use when seeing unique_constraint…
- ▌ Assigns Audit · oliver-kriskaInspect LiveView socket assigns for memory bloat — missing temporary_assigns, unused assigns, unbounded lists needing streams, memory estimates. Use when LiveView memory grows or you need to add temporary_assigns.
- ▌ Learn From Fix · oliver-kriska bundleCapture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
- ▌ Mix Compression · oliver-kriska bundleReduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.
- ▌ Recall · oliver-kriska bundleRecall prior work from past sessions — how a bug was fixed, what was decided, where a pattern lives. Use when asked 'have we done this before' or 'how did I fix X' in Elixir/Phoenix work. ccrider MCP when available, else git + solution docs.
- ▌ Review · oliver-kriska bundleReview code with parallel agents — tests, security, Ecto, LiveView, Oban. Use after implementation to catch bugs and anti-patterns before committing.
- ▌ Triage · oliver-kriska bundleTriage review findings interactively — approve, skip, or prioritize each issue. Use after /phx:review to filter findings before fixing.
- ▌ Verify · oliver-kriska bundleVerify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.