4riel

Runtime adapter guidance for the docko repository. Use when working on runtime-specific packages, template installers, hook flows, snippet assets, runtime documentation, or when extending support beyond the current Claude Code adapter.

Use when working in a persistent-slot workspace that uses docko. Covers slot claims, delegated teammate inheritance, and the rule that code edits inside slots/ require an active claim.

Documentation and docs-sync guidance for the docko repository. Use when editing README, docs, examples, snippets, onboarding guides, or public positioning so the written guidance stays aligned with the implemented protocol and adapters.

Protocol, schema, and CLI contract guidance for the docko repository. Use when changing registry or session shapes, claim and delegation behavior, stale cleanup, authorization, or the public CLI behavior that reflects those semantics.

Repository onboarding and working conventions for the docko monorepo. Use when an agent needs to understand the repo layout, choose the right docs or commands, plan a change, or verify work without crossing the core, cli, adapters, docs, and tests boundaries.

Mandatory knowledge lookup protocol for all tax agents. Defines the 4-level search hierarchy (local → official → unofficial → unknown) that every agent must follow before answering any fiscal question.

Complete guide for navigating Marangatu portal (Paraguay tax system). Covers login, AngularJS sidebar navigation, form field mapping, invoice emission, and error recovery. Used by browser automation agents.

How to save, load, and manage tax filing records. Covers directory structure, summary.json schema, screenshot conventions, and annual totals. Used by agents that need to persist or read operation results.

Legal framework, tax rules, exemption criteria, and filing procedures for Paraguayan fiscal obligations. Covers Ley 6380/2019, IVA treatment, IRP rules, progressive rates, and filing sequence. Used by all agents that make fiscal decisions.

Complete taxpayer and client data for fiscal operations. Contains identity, RUC, address, client details, tax treatment, and billing configuration. Used by agents that need to fill forms or verify taxpayer info.

This skill should be used when debugging a bug, error message, or test failure — tracing root cause, generating and ranking hypotheses, or when stuck/looping and needing an escalating strategy (step back, compare plans, naive-first, ultrathink). Contains Shumer's 9-step framework and 4 escalating techniques for getting unstuck.

This skill should be used when planning implementation work before writing code — drafting a plan, reviewing one as a staff engineer, structuring unresolved questions and success criteria, comparing two competing approaches, or ordering phases by dependency and risk. Contains plan formats, evaluation criteria, and the two-plan comparison technique.

This skill should be used when rewriting a vague or imperative prompt into a declarative, exhaustive, verification-driven one — expanding scope, injecting test/lint/build verification commands, defining completion criteria, or auditing UI and cross-cutting changes for full coverage. Contains exhaustiveness rules, verification patterns, and anti-patterns to fix.

This skill should be used when practicing test-driven development — writing one failing test at a time through RED-GREEN-REFACTOR, designing testable interfaces, deciding what to mock versus what not to mock, or choosing between pass@k and pass^k test strategies. Contains vertical-slicing rules and testing anti-patterns to avoid.