b00t-interface-library
Design and implement a Rust interface library in l3dg3rr that acts as a feature-configurable lifecycle manager for b00t processes. The library compliantly implements init → operate → terminate → lifecycle maintenance of miscellaneous process surfaces (MCP servers, daemons, sidecars) with deterministic governance controls. Uses the autoresearch pattern (karpathy/autoresearch): agent reads program.md, iterates on the library, experiments autonomously.
What this skill does
## Overview
The b00t interface library (`crates/b00t-iface/`) is the Rust analog of
`train.py` in karpathy/autoresearch. It is the single file the agent modifies
and improves. The "research loop" is:
```
program.md (this skill) ──→ agent
↓ iterates on
b00t-iface/src/lib.rs (single-file interface library)
↓ tested by
cargo test -p b00t-iface (5-minute eval budget)
↓ keep/discard based on
test results + coverage + lint pass
```
## Core Trait: `ProcessSurface`
The library provides one primary trait and one lifecycle manager:
```rust
/// A process surface is any executable that can be started, checked,
/// and stopped by the b00t hive. Examples: MCP servers, sidecars,
/// daemons, one-shot scripts.
pub trait ProcessSurface {
type Config: Deserialize;
type Error: std::error::Error;
type Handle;
/// Declare what this surface needs before it can run.
fn requirements(&self) -> Vec<Requirement>;
/// Init: validate config, resolve dependencies, acquire resources.
fn init(&mut self, config: Self::Config) -> Result<(), Self::Error>;
/// Operate: start the process, return a handle for lifecycle control.
fn operate(&self) -> Result<Self::Handle, Self::Error>;
/// Terminate: graceful shutdown, resource release, audit record.
fn terminate(handle: Self::Handle) -> Result<AuditRecord, Self::Error>;
/// Lifecycle maintenance: health check, restart policy, log rotation.
fn maintain(&self) -> MaintenanceAction;
}
```
## Governance Controls
Each surface declares a `GovernancePolicy`:
```rust
pub struct GovernancePolicy {
/// Which agents/roles are allowed to start this surface.
pub allowed_starters: Vec<AgentRole>,
/// Maximum runtime before forced re-evaluation.
pub max_ttl: Duration,
/// Whether this surface can be restarted automatically.
pub auto_restart: bool,
/// Crash threshold before surface is quarantined.
pub crash_budget: u32,
}
```
## Autoresearch Loop
The agent follows this loop autonomously:
1. **Read** this skill and the current `crates/b00t-iface/src/lib.rs`
2. **Modify** `lib.rs` — add a new surface impl, improve governance, fix invariant
3. **Run** `cargo test -p b00t-iface 2>&1 | tail -20` (the 5-minute eval)
4. **Keep** if tests pass AND new coverage > 80%
5. **Discard** if tests fail — revert with `git checkout -- crates/b00t-iface/`
6. **Log** the experiment outcome in `EXPERIMENTS.md`
7. **Repeat** until user halts or 100 experiments reached
## First Experiment
The first surface to implement: the **datum file watcher** — a daemon that
watches `_b00t_/datums/` for changes and re-validates the invariant schema.
This proves the init → operate → terminate → maintain cycle with a real b00t
resource.
## Interfaces
The library decomposes into:
| Module | Purpose | Status |
|--------|---------|--------|
| `surface` | `ProcessSurface` trait + `LifecycleManager` | Design |
| `governance` | `GovernancePolicy`, agent roles, crash budget | Design |
| `datum_watcher` | Datum file watcher surface | First target |
| `audit` | `AuditRecord` type for termination events | Design |
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.