Results for “packages”

Use ONLY for code review and test write/review guidance in `packages/agent-core-v2` (the DI × Scope agent engine). Does NOT apply to the legacy `packages/agent-core` or to any other package — for those, do not load this skill. Groups the review and testing lenses used for agent-core-v2 — `slop` (single-level-of-abstraction / layered error-handling review, invoked only on explicit request) and `test` (contract-driven per-test rules for both authoring and reviewing tests). Apply the sub-skill that matches the task; do not apply `slop` unprompted.

Inspect package metadata, lockfiles, scripts, and npm release readiness.

Index and search code repositories, documentation, research papers, HuggingFace datasets, local folders, and packages via the Nia API, with AI-powered research and code advisor capabilities.

Build the smallest, highest-signal context package for an AI coding task — goal, constraints, repo facts, boundaries, and a verification plan. Load when prompts are underspecified, the agent is missing key files or decisions, the user says "use the right context", "here's the repo", or when work is drifting due to missing constraints. Also triggers on "context engineering", "gather context", "what do you need from me", "before you start". Not for cross-session continuity (use memory-startup/memory-recall).

Build a task-aware context bundle (relevant code + applicable standards + related past decisions) via the local RAG index, capped at a token budget. Use at the start of any implementation/refactor/debug task instead of reading files blindly. Replaces "read whole file" with "retrieve the function + callers + rules + prior ADR."

Builder of templates, prompt packs, kits, swipe files, and reusable digital assets. Trigger when user requests 'create template', 'build prompt pack', 'assemble digital kit', 'make swipe file', or 'produce reusable assets'.

AI coding agents fail in consistent, predictable ways. They fabricate npm packages that don't exist. They catch errors and continue silently. They add features you never asked for. They lose context mid-session and forget what they were doing.

Cheshire Skills Store index — curated Agent Skills packages for Cheshire Terminal (API, PostHog, Google Agent Registry, Skill Hub onchain, Stripe, Solana common errors, NOXA) plus the community skills collection. Use when installing store skills, browsing the store catalog, or wiring cheshireterminal.ai/skills-store.

Canonical kip knowledge-store patterns for any process or agent: recall prior facts before work, assert decisions/gate outcomes/rejections as structured facts after work, resolve entities with explicit --model sonnet, and invoke the CLI Windows-safely via node packages/kip-sdk/dist/cli/kip.js when kip is not on PATH.

Guided installation of the Roots AI stack (roots/acorn-ai + wordpress/mcp-adapter) in a Sage/Bedrock project via Lando. Runs detect-ai-readiness probe, identifies gaps, installs missing packages, publishes Acorn AI config, writes API key to .env, generates .mcp.json, validates MCP handshake via discover-abilities. Invoke for: ai-setup, install acorn ai, mcp adapter, install mcp, setup mcp, ai stack, discover-abilities not working, wordpress mcp, acorn-ai setup.

Use when developing in packages/agent-core-v2 (the DI × Scope agent engine) — adding or modifying a domain Service, choosing a LifecycleScope, wiring DI dependencies, splitting a domain across scopes, owning or migrating a config section, gating behavior behind an experimental flag, raising coded errors, working on the permission system, writing DI/Scope tests, porting business logic from agent-core (v1) to v2, triaging a main-branch commit against v2, or exposing a v2 domain over server-v2 while keeping the /api/v1 wire contract compatible with released clients. Self-contained guide organized by development stage (orient → design → implement → test → verify) plus align workflows for v1→v2 migration, main-branch commit triage, and server-v2 wire exposure; each file carries the rules, examples, and red lines for its step.