en un clic
brainiac
brainiac contient 4 skills collectées depuis xkazm04, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
Connect this repository to the org's Brainiac memory. Pairs the repo with the Brainiac console (device-flow approval), writes a project-scoped API key into .env without ever displaying it, verifies connectivity end to end, enriches CLAUDE.md/AGENTS.md with memory conventions, and optionally registers the MCP server and syncs the org's skill library. Safe to re-run.
Session-after-session product perfection loop. The strongest available model (Fable) directs — it walks the repo's context map context-by-context, proposes 5 challenged, high-value directions per context (features, design elevations, significant optimizations), gates them with the user until 10 are accepted, then orchestrates builder subagents (model sized to the work — Sonnet for S/M briefs, Opus for L or high-risk ones) per context in isolated worktrees while making every review/merge decision itself. All state lives in a linked Obsidian vault so any future session resumes the loop exactly where the last one stopped. Invoke with `/perfect [init|propose|build|status|reflect] [context-name]`.
Simulated User Acceptance Testing for Brainiac, run as a controlled trial inside a simulated multi-stack engineering company rather than a feature walkthrough. Characters are developers (Rust/TS/Python/infra) doing real coding work; every journey runs in three arms — cold agent, Claude's native local memory (the free baseline), and Brainiac — and the verdict is the DELTA, which is allowed to come out negative. Two chronological certification levels: L1 theoretical (over a code-derived model of what an agent actually receives, cheap + mass-parallel) then L2 empirical (live server + workers + real agent sessions against the Meridian company). Ships a Harm Ledger alongside findings. Per-run specifics live in the repo's uat/ overlay. Invoke with `/uat init|update|run|promote [args]`.
Iteratively prototype a console page/component through directional variants behind a tab switcher, then consolidate the winner. Use when the user wants to explore multiple design approaches for a Brainiac console surface (visual appeal, creativity, UX clarity).