prime-radiant-inc
- 50 skills
- 0 followers
- 9 hours ago last updated
- ▌ Using Kitchen Sink · prime-radiant-incUse when starting any conversation - explains the kitchen-sink fixture plugin's capabilities
- ▌ Using Ledger · prime-radiant-incUse when work spans sessions or agents and needs durable, verifiable state — starting multi-session or multi-agent work, dispatching subagent fleets, resuming after context death, handing off, tracking an investigation, running an issue board, picking unblocked work, or deciding "should this be a ledger?". Teaches when and how to use the `chit` CLI's patterns; command mechanics live in `chit quickstart`.
- ▌ Ledger Issues · prime-radiant-incUse when working a shared ledger issue board — picking and claiming tasks, closing with evidence, breaking cycles, and reconciling contested state after sync.
- ▌ Parallel Adversarial Review · prime-radiant-inc bundleUse when reviewing a diff, commit, branch, or implementation against a spec — dispatches two same-model reviewer subagents in parallel under a competitive scoring frame, then aggregates findings. Triggers on "review this", "PAR review", "adversarial review", or any evaluative gate (scope review, spec compliance, code quality, audit).
- ▌ Multi Model Adversarial Review · prime-radiant-inc bundleUse for high-stakes review where you want multiple model providers reviewing the same artifact and critiquing each other. Shells out to installed coding-agent CLIs (claude, codex, gemini, pi, opencode by default; amp and droid available opt-in) to run parallel reviews, then runs a cross-critique grid where each reviewer evaluates the others' findings to catch hallucinations and severity inflation, then synthesizes a final deduplicated report. Triggers on "MMAR review", "multi-model review", "cross-model adversarial", "review with all the models", or when single-model PAR feels insufficient.
- ▌ Tool Fluency · prime-radiant-incUse when designing, running, or diagnosing Evener tool-fluency experiments for a real built-in, plugin, or newly added tool. Covers probe manifests, model comparisons, semantic oracles, and interpreting fluency failures without ad-hoc transcript parsing.
- ▌ Fuzzing An API Surface · prime-radiant-incUse when a surface parses untrusted or model-generated input — a wire protocol, tool-call JSON, upstream SSE, an HTTP body — or after a parser/dispatch bug, to fuzz that surface and turn any deterministic failure into a permanent, flake-guarded regression test. Covers picking a seam, choosing oracles beyond "no panic", the portable promoter/schema-generator core, and the safety bounds that keep a fuzzer from executing dangerous handlers.
- ▌ Doctoring Evener · prime-radiant-inc bundleUse when diagnosing a evener session, job, watch, or the session tree — investigating watch runaways (self-influence depth + runaway-fuse drops), dropped/coalesced deliveries, "how many times did X actually get called", stuck turns, or parent↔delegate↔observer linkage. Covers the evener doctor forensic tools, the Finding contract, runbook authoring, and graduated repair.
- ▌ Debug Run · prime-radiant-incUse when a toil run has failed or produced unexpected results and you need to investigate what happened
- ▌ Watch Run · prime-radiant-incUse when monitoring an in-progress toil run, checking if a run is stuck, or observing live workflow execution
- ▌ Building Workflows · prime-radiant-incUse when writing, editing, validating, or debugging toil workflow YAML — node/edge structure, ForEach, decision tags, expression syntax (${workflow_input.X} vs ${input.X}, supported node fields, required ! refs), or analyzing why a run misbehaved
- ▌ Auditing Progress · prime-radiant-inc bundleUse when an iteration has just finished and you need to verify behavior evidence quality in three tiers — deep evidence for current stories, impacted behavior for touched scenarios, and sentinel corpus for high-value regression detection.
- ▌ Implementing Tasks · prime-radiant-inc bundleUse when executing a batch of TDD-sized tasks inside a running-an-iteration call — dispatches an implementer subagent per task following red-green-refactor discipline and returns per-task completion status.
- ▌ Running An Iteration · prime-radiant-inc bundleUse when executing the next pending iteration from an iterative-development roadmap — picks the iteration, decomposes into code and evidence tasks, runs sentinel corpus baseline, dispatches implementing-tasks, runs impacted + sentinel scenarios, and updates artifacts.
- ▌ Iterative Development · prime-radiant-incUse when implementing a project with a large, comprehensive, or ambiguous spec — extracts requirements with proof obligations, defines a walking skeleton with its first journey scenario, then loops through audited sprints that continuously build a behavior evidence corpus. Completion means passing evidence, not just finished stories.
- ▌ Extracting Requirements · prime-radiant-inc bundleUse when starting an iterative-development run on human spec collateral — reads the spec, produces per-epic requirement files with proof obligations and behavior scenario cards with stable IDs.
- ▌ Scoping The Simplest Core · prime-radiant-inc bundleUse when turning extracted requirements into a roadmap — selects the walking skeleton iteration with its first journey scenario, orders remaining work into follow-on iterations, and applies story splitting when ACs have different dependency profiles.
- ▌ Reading A Book · prime-radiant-inc bundleUse when reading a book, paper, RFC, long essay, or any sustained written work your human partner wants you to understand and apply later — when the goal is comprehension and durable use, not lookup or skim.
- ▌ Holding Beliefs · prime-radiant-incUse when catching yourself making a load-bearing claim you haven't named as a belief; unable to articulate why you're invoking a skill; noticing a defendable pattern across your own work; feeling unnamed resistance to a claim while reading; finishing a chapter, coherent argument, or zettel-extraction sweep; receiving a research subagent's report; hitting a debugging surprise or substantive pushback from your human partner; before committing to a substantive recommendation, plan, or extraction; or starting non-trivial work in a domain with prior beliefs.
- ▌ Taking Smart Notes · prime-radiant-inc bundleUse when reading or working produces a durable insight worth keeping past the current session, when extracting ideas from a finished per-source note, or when a claim deserves a permanent home in the slip-box (atomic notes, zettels, Zettelkasten).
- ▌ Writing From Notes · prime-radiant-incUse when starting a substantive piece of writing — essay, summary, post, design doc, blog draft — where the topic has been encountered in past reading or work.
- ▌ Learning From Experience · prime-radiant-incUse mid-task when something procedurally interesting just happened — a skill's procedure didn't fit the situation, a novel approach worked, a failure-then-recovery taught something, a source or your human partner's critique bears on an existing skill, or a procedural surprise resists naming.
- ▌ Reflecting On Experience · prime-radiant-incUse at deliberate reflection moments — finishing significant work, unconsumed experience entries having accumulated in notes/experience/ since the last pass, a notable success or failure involving a skill, teaching forcing you to articulate what you do, or picking up a skill after time away.
- ▌ Deliberating Under Ambiguity · prime-radiant-incUse at decision points where the proposed action is non-trivial (high blast radius, hard reversibility, work that branches on early choices, or goal ambiguity) AND the situation is ambiguous — multiple interpretations or response shapes plausibly fit, or a recognition rubric flagged ambiguity.
- ▌ Writing Skills From Learning · prime-radiant-inc bundleUse when you've just read a source (book, course, paper) that teaches a named procedure, technique, or move-sequence, and the procedural detail is fresh in working memory — or when a reflecting-on-experience pass has just concluded the experience log points at a missing skill.
- ▌ Doc Research · prime-radiant-incPublic documentation extraction methodology. Search sequence (3 tiers), behavioral claim extraction rules, output structure, termination criteria, and gap analysis. Loaded by the analyzer agent for documentation research.
- ▌ Binary Analysis · prime-radiant-incLayer 1 methodology for extracting behavioral intelligence from compiled binaries, bytecode archives, managed assemblies, and bundled applications. Covers artifact identification, string extraction strategy, decompilation workflows, provenance requirements, and handoff to source code mode.
- ▌ Git Archaeology · prime-radiant-incLayer 1 skill for mining git history for behavioral intelligence. Repository overview, commit message mining, PR/MR description extraction, blame-based maintenance heat maps, issue tracker cross-referencing. Loaded by the analyzer agent during Layer 1.
- ▌ Source Analysis · prime-radiant-incLayer 1 skill for source code analysis — decompose any codebase into analyzable units, extract behavioral claims with provenance. Supports three target shapes (source tree, bundle, decompiled binary), with per-language grep patterns and analysis templates.
- ▌ Analysis Pipeline · prime-radiant-incReverse engineering - multi-source product intelligence analysis with provenance tracking. Master methodology for all analysis agents.
- ▌ Spec Sanitization · prime-radiant-incSanitizes analysis specs to remove implementation contamination while preserving provenance metadata. Run in SEPARATE SESSION after analysis, before implementation.
- ▌ Contract Detection · prime-radiant-incLayer 1 skill for parsing machine-readable API contracts. OpenAPI/Swagger, GraphQL, Protobuf/gRPC, and JSON Schema detection, extraction, and behavioral claim generation. Loaded by the analyzer agent during Layer 1.
- ▌ Ecosystem Analysis · prime-radiant-incLayer 1 skill for SDK and ecosystem analysis. SDK discovery strategy, behavioral extraction methodology, integration test mining, output formats. Loaded by the analyzer agent for SDK and ecosystem work.
- ▌ Second Pass Review · prime-radiant-incIndependent audit of sanitized specs in workspace/output/. Three parallel LLM-based reviewer roles check structural leakage, content contamination, and behavioral completeness. Run AFTER Layer 5 sanitization, BEFORE implementation handoff.
- ▌ Visual Exploration · prime-radiant-incLayer 1 skill for browser automation and visual UX documentation. Initial reconnaissance, navigation mapping, interaction documentation, end-to-end flow capture, edge case exploration, screenshot methodology. Loaded by the analyzer agent during Layer 1.
- ▌ Container Execution · prime-radiant-incInfrastructure skill for containerized target execution. Runtime detection, container lifecycle, security restrictions, interaction patterns.
- ▌ Fidelity Validation · prime-radiant-incCross-validates sanitized output specs against raw source specs to detect lost behavioral detail, dropped constants, missing features, or diluted precision. Run AFTER sanitization and AFTER contamination audit passes.
- ▌ Runtime Observation · prime-radiant-incCross-cutting skill for runtime observation methodology. Five-phase observation discipline, container interaction patterns, observation record format, claim extraction, environment variation. Loaded by the analyzer agent for runtime observation roles.
- ▌ Source Completeness · prime-radiant-incValidates that all user-facing surfaces discovered in source code are captured in the behavioral specs. Catches coverage gaps where the analysis pipeline missed features, tools, env vars, CLI flags, or other behavioral interfaces. Run AFTER Layer 3 specs are written, BEFORE sanitization.
- ▌ Test Suite Analysis · prime-radiant-incLayer 1 skill for extracting behavioral intelligence from test suites. Framework detection, test code reading strategy, test execution strategy, behavioral claim extraction with Given/When/Then mapping, e2e vs unit value classification. Loaded by the analyzer agent during Layer 1.
- ▌ Autonomous Discovery · prime-radiant-incLayer 1 intelligence source discovery - auto-detect available sources, search for public information, negotiate with user, produce inventory manifest
- ▌ Incremental Analysis · prime-radiant-incDetect existing workspace, diff current sources against high water mark metadata, classify specs as unchanged/stale/orphaned/new, re-analyze only what changed. Activates automatically when /analyze finds an existing workspace.
- ▌ Community Intelligence · prime-radiant-incLayer 1 skill for community intelligence gathering. Search channels, extraction methodology, consensus analysis, version-aware behavioral changes, structural contamination guard. Loaded by the analyzer agent for community intelligence gathering.
- ▌ Multi Source Synthesis · prime-radiant-incLayer 2 synthesis methodology. Feature discovery, architecture reverse engineering, API extraction, cross-source synthesis with conflict resolution, module mapping. Transforms raw Layer 1 intelligence into structured synthesis documents. Loaded by the analyzer agent during Layer 2.
- ▌ Provenance Methodology · prime-radiant-incCross-cutting provenance discipline. Citation format, confidence levels, source hierarchy, session capture. Loaded by every analysis agent.
- ▌ Validation Methodology · prime-radiant-incCross-cutting validation discipline. Acceptance criteria format, definition of done checklists, quality gate criteria, verification methods. Loaded by every analysis agent.
- ▌ Behavioral Spec Writing · prime-radiant-incLayer 3 deep documentation methodology. Per-module behavioral specifications, external and behavioral integration contracts, behavior documentation, end-to-end user journey analysis. Transforms Layer 2 synthesis into implementable behavioral specifications. Loaded by the analyzer agent during Layer 3.
- ▌ Linear · prime-radiant-incManage Linear issues. Use when asked about tasks, tickets, bugs, or Linear.
- ▌ Writing Gauntlet Stories · prime-radiant-incUse when writing or reviewing a Gauntlet story card. Establishes the calibration framing — outcomes, persona binding, observable acceptance criteria — and explicitly rules out wrong-shaped frames (Agile user stories, QA step-scripts, BDD Given/When/Then) so prior knowledge does not contaminate the card.
- ▌ Proving It Works With A Movie · prime-radiant-inc bundleUse when asked for a demo, screencast, tutorial, walkthrough, or proof video of software actually running, when a reviewer needs to see a feature work rather than take your word for it, or when handing over any video artifact of app behavior