Skills Directory
Claude Skills by Andersseen
github.com/AndersseenAdd a pack to the Agentyx built-in registry (packages/core/src/pack/registry.ts) with the registry and resolver tests it needs. Use when asked to add, rename or re-categorize a built-in pack such as technical, typescript, angular, efficiency or agentic.
Develop Agentyx with targeted exploration, narrow iteration commands, concise output, and full verification before handoff.
Navigate the Agentyx repository by package responsibility so changes start in the right place.
Build the official Agentyx website with token-frugal discovery, grounded product copy, and visual verification.
Use Agentyx repository AI tooling in a provider-neutral, token-frugal way.
Run the full Agentyx verification pipeline before handing work back - formatting, typecheck, tests, build, and the CLI behaviour checks that pnpm check does not cover. Use after any change to packages/core, packages/cli, or the config schema.
<!DOCTYPE html><html lang="en"><head> <meta charset="utf-8"> <title>Volt UI</title> <base href="/"> <script> // Applies the visitor's saved theme before first paint so there is no // flash of the default (volt/sharp/light) theme while Angular loads. // This mirrors src/app/components/theme-switcher.ts's localStorage // keys; keep both in sync if those keys ever change. Runs unguarded // because it only ever executes in the browser (a raw <script> tag // is never evaluated by Angular's server ...
Add a pack to the Agentyx built-in registry (packages/core/src/pack/registry.ts) with the registry and resolver tests it needs. Use when asked to add, rename or re-categorize a built-in pack such as technical, typescript, angular, efficiency or agentic.
Develop Agentyx with targeted exploration, narrow iteration commands, concise output, and full verification before handoff.
Navigate the Agentyx repository by package responsibility so changes start in the right place.
Build the official Agentyx website with token-frugal discovery, grounded product copy, and visual verification.
Use Agentyx repository AI tooling in a provider-neutral, token-frugal way.
Run the full Agentyx verification pipeline before handing work back - formatting, typecheck, tests, build, and the CLI behaviour checks that pnpm check does not cover. Use after any change to packages/core, packages/cli, or the config schema.
Structure Angular features with clear boundaries, DI, OnPush, and accessibility.
Use current Angular APIs for standalone components, control flow, inputs, outputs, and DI.
Use Angular signals for local synchronous state and derived values.
Test Angular behavior with appropriate unit, component, and E2E boundaries.
Design small explicit APIs with stable contracts and useful errors.
Document interfaces so a caller can use them without reading the source.
Apply ARIA only where native semantics fall short, and keep state accurate.
Separate authentication from authorization and enforce both server side.
Clarify ambiguous feature work before committing to an implementation path.
Keep branches short-lived and integrate continuously.
Build pipelines that are fast, reproducible and trusted.
Keep code clear, local, and purposeful while changing existing systems.
Review meaningful changes for correctness, regressions, security, tests, and complexity.
Make each commit a single reviewable change with a useful message.
Communicate technical progress and results compactly without losing important details.
Build small, reproducible and non-privileged container images.
Develop with targeted discovery, narrow iteration, and complete verification.
Design schemas that make invalid states unrepresentable.
Record significant technical decisions with their context and consequences.
Keep the dependency graph small, current and pointing one way.
Vet, pin and update third-party dependencies deliberately.
Release in small increments with a fast, tested way back.
Write end-to-end tests that are few, critical and stable.
Apply maintainable software-engineering judgment to non-trivial code changes.
Diagnose and fix non-deterministic tests instead of retrying them.
Choose narrow checks while iterating and full required gates before completion.
Restore service first, diagnose second, and learn without blame.
Define infrastructure declaratively, in version control, applied automatically.
Make every interaction reachable, visible and escapable by keyboard.
Work safely in unfamiliar code with weak or missing tests.
Instrument systems so failures are visible before users report them.
Split independent coding-agent work safely when tasks do not overlap.
Measure before optimizing and confirm the gain after.
Plan non-trivial work before editing, and keep small changes small.
Size and present changes so they can actually be reviewed.
Diagnose slow database access with query plans, indexes and access patterns.
Change structure without changing behavior, in reversible steps.