2389-research

@2389-research source repo

43 skills
0 followers
13 hours ago last updated

▌
CSS Development Refactor · 2389-research
This skill should be used when refactoring existing CSS from inline styles or utility classes to semantic patterns. Triggers on "refactor CSS", "extract styles", "consolidate CSS", "convert inline", "clean up styles", "migrate to semantic". Transforms to semantic classes with dark mode and tests.

0
installs
▌
CSS Development Validate · 2389-research
This skill should be used when reviewing or auditing existing CSS code for consistency with established patterns. Triggers on "review CSS", "audit styles", "check CSS", "validate stylesheet", "CSS review". Checks semantic naming, dark mode coverage, Tailwind usage, and test coverage.

0
installs
▌
CSS Development Create Component · 2389-research
This skill should be used when creating new styled components or adding new CSS classes. Triggers on "create component", "new button", "new card", "add styles", "style component", "build UI element". Guides semantic naming, Tailwind composition, dark mode support, and test coverage.

0
installs
▌
Git Repo Prep · 2389-research
Use when preparing a codebase for public/open-source release, reviewing a repo for openness, or auditing for secrets and missing documentation before making code public. Triggers on "open source", "public release", "prepare repo", "openness", "repo review", "make public", "open-source prep".

0
installs
▌
Review · 2389-research
Use when auditing a codebase for openness, checking for secrets, missing docs, or gaps before public release. Re-runnable at any point.

0
installs
▌
Prepare · 2389-research
Use when preparing a codebase for first-time public/open-source release. Full lifecycle from audit through documentation, hardening, and final review.

0
installs
▌
Prbuddy · 2389-research
PR health assistant - monitors CI status, triages review comments, fixes issues with systematic prevention. Triggers on "check my PR", "PR health", "make PR green", "fix PR", "ready to merge", "handle PR feedback".

0
installs
▌
Prbuddy CI · 2389-research
CI/workflow monitoring and fixing. Triggers on "CI failing", "workflow failed", "checks red", "build broken", "tests failing", "rerun workflows".

0
installs
▌
Prbuddy Reviews · 2389-research
Review comment triage and handling. Triggers on "review comments", "address feedback", "reviewer asked", "changes requested", "handle comments", "triage reviews".

0
installs
▌
Firebase Development Debug · 2389-research
This skill should be used when troubleshooting Firebase emulator issues, rules violations, function errors, auth problems, or deployment failures. Triggers on "error", "not working", "debug", "troubleshoot", "failing", "broken", "permission denied", "emulator issue".

0
installs
▌
Firebase Development Validate · 2389-research
This skill should be used when reviewing Firebase code against security model and best practices. Triggers on "review firebase", "check firebase", "validate", "audit firebase", "security review", "look at firebase code". Validates configuration, rules, architecture, and security.

0
installs
▌
Firebase Development Add Feature · 2389-research
This skill should be used when adding features to existing Firebase projects. Triggers on "add function", "create endpoint", "new tool", "add api", "new collection", "implement", "build feature". Guides TDD workflow with test-first development, security rules, and emulator verification.

0
installs
▌
Firebase Development Project Setup · 2389-research
This skill should be used when initializing a new Firebase project with proven architecture. Triggers on "new firebase project", "initialize firebase", "firebase init", "set up firebase", "create firebase app", "start firebase project". Guides through CLI setup, architecture choices, and emulator configuration.

0
installs
▌
Deliberation · 2389-research bundle
Use when facing decisions requiring careful consideration - ethical questions, architecture choices, trade-offs, or when user has a stake and wants to participate in finding clarity. Routes to discernment (internal), clearness (multi-agent), or gathered (participatory).

0
installs
▌
Deliberation Gathered · 2389-research
Use when user has a stake or perspective in a decision and wants to participate in discernment rather than receive advice - facilitates user alongside agent voices with participatory discipline teaching

0
installs
▌
Deliberation Clearness · 2389-research
Use when a question needs parallel deep analysis from multiple perspectives - code reviews, architecture decisions, research synthesis - spawn specialized agents as a clearness committee rather than doing everything in one context

0
installs
▌
Deliberation Discernment · 2389-research
Use when facing questions with ethical weight, multiple valid approaches, significant trade-offs, or potential for harm - before answering, convene internal voices to discern rather than conclude

0
installs
▌
Experts · 2389-research
Use when a project needs multi-perspective review — pre-launch audit, post-refactor check, inherited codebase assessment, or periodic health check. Dispatches parallel expert reviewer agents with persona framing.

0
installs
▌
Normies · 2389-research
Use when you want to see a site through fresh eyes — how different types of people experience it for the first time. Dispatches agents with varying tech sophistication who land on the site cold and report confusion, friction, and first impressions.

0
installs
▌
Regulars · 2389-research
Use when you want to verify a site works by having agents act as real users completing common tasks — browsing, subscribing, purchasing, searching. Each agent has a goal and clicks through the real flow using browser MCP tools.

0
installs
▌
Well Actually · 2389-research
Use when you want pedantic, nitpicky, opinionated feedback on a site or project — the kind of feedback you'd get from Hacker News commenters, typography snobs, grammar pedants, and standards purists. Finds the things that professional reviewers skip because they're "too minor."

0
installs
▌
Binary Re Triage · 2389-research
Use when first encountering an unknown binary, ELF file, executable, or firmware blob. Fast fingerprinting via rabin2 - architecture detection (ARM, x86, MIPS), ABI identification, dependency mapping, string extraction. Keywords - "what is this binary", "identify architecture", "check file type", "rabin2", "file analysis", "quick scan"

0
installs
▌
Binary Re Synthesis · 2389-research
Use when ready to document findings, generate a report, or summarize binary analysis results. Compiles analysis findings into structured reports - correlates facts from triage/static/dynamic phases, validates hypotheses, generates documentation with evidence chains. Keywords - "summarize findings", "generate report", "document analysis", "what did we find", "write up results", "export findings"

0
installs
▌
Binary Re Tool Setup · 2389-research
Use when reverse engineering tools are missing, not working, or need configuration. Installation guides for radare2 (r2), Ghidra, GDB, QEMU, Frida, binutils, and cross-compilation toolchains. Keywords - "install radare2", "setup ghidra", "r2 not found", "qemu missing", "tool not installed", "configure gdb", "cross-compiler"

0
installs
▌
Binary Re Static Analysis · 2389-research
Use when analyzing binary structure, disassembling code, or decompiling functions. Deep static analysis via radare2 (r2) and Ghidra headless - function enumeration, cross-references (xrefs), decompilation, control flow graphs. Keywords - "disassemble", "decompile", "what does this function do", "find functions", "analyze code", "r2", "ghidra", "pdg", "afl"

0
installs
▌
Binary Re Dynamic Analysis · 2389-research
Use when you need to run a binary, trace execution, or observe runtime behavior. Runtime analysis via QEMU emulation, GDB debugging, and Frida hooking - syscall tracing (strace), breakpoints, memory inspection, function interception. Keywords - "run binary", "execute", "debug", "trace syscalls", "set breakpoint", "qemu", "gdb", "frida", "strace", "watch memory"

0
installs
▌
Speed Run · 2389-research
Token-efficient code generation pipeline using hosted LLM. Triggers on "speed-run", "fast build", "turbo build", "use hosted LLM", "use cerebras". Routes to turbo (direct codegen), showdown (parallel competition), or any% (parallel exploration).

0
installs
▌
Judge · 2389-research
Scoring framework for speed-run showdown and any-percent. Invoked at Phase 4 to evaluate implementations using 5-criteria scoring. Do not invoke directly - called by showdown/any-percent.

0
installs
▌
Turbo · 2389-research
Direct code generation via hosted LLM (Cerebras). Write a contract prompt, generate code, fix surgically. Part of speed-run pipeline.

0
installs
▌
Showdown · 2389-research
Same design, multiple parallel runners compete using hosted LLM for code generation. Each runner creates own plan, generates code via Cerebras, pick the best. Part of speed-run pipeline.

0
installs
▌
Any Percent · 2389-research
Explore different architectural approaches in parallel using hosted LLM for code generation. No restrictions on approach - fastest path to comparing real implementations. Part of speed-run pipeline.

0
installs
▌
Thrifty · 2389-research bundle
Use when the user says "thrifty", "delegate this", "tiered build", or asks to execute a spec cheaply. thrifty takes a spec you already have (written by hand or by any model — thrifty doesn't care which) and EXECUTES it for less. Orchestrates a tiered-delegation run: the architect (Sonnet) refines the spec into a contract that pins every cross-cutting decision, ONE cached Haiku executor subagent builds the whole ordered unit list in a single session (gate in-loop, self-fixing — not one subagent per unit), and Sonnet verifies/fixes only where a test can't judge. Works for code and non-code tasks alike. PREFER the lean dispatch flow (thrifty-dispatch) by default — it is the benchmarked, cheapest path; THIS subagent substrate is the richer, pricier fallback.

0
installs
▌
Thrifty Plan · 2389-research
Planning discipline for thrifty, run by the architect (Sonnet) itself. Decomposes a task into units, writes CONTRACT.md (cross-unit decisions + dependency graph), one self-contained BRIEF per unit with concrete acceptance criteria, and initializes the LEDGER. Invoked by the thrifty orchestrator during the Plan step.

0
installs
▌
Thrifty Brief · 2389-research
Brief-writer subskill for thrifty's split planning mode. Expands ONE terse unit spec (from the architect/director) plus the shared contract into a full, self-contained BRIEF with right-sized approach and concrete acceptance criteria. Has authority WITHIN its unit only; never re-decides anything the contract already pins. Do not invoke directly — dispatched as a Sonnet subagent by the thrifty orchestrator.

0
installs
▌
Thrifty Check · 2389-research
Checker subskill for thrifty. Verifies one completed unit against its acceptance criteria, attempts a surgical fix for small localized defects, and returns a structured verdict that diagnoses the failure so the orchestrator can route it. Do not invoke directly — dispatched as a Sonnet subagent by the thrifty orchestrator.

0
installs
▌
Thrifty Execute · 2389-research
Executor subskill for thrifty. ONE cached agent that builds an ordered list of units from their briefs in a single session — honoring the shared contract, running the gate, and self-fixing — then reports per-unit results. (Also handles the degenerate single-unit case.) Do not invoke directly — dispatched as a Haiku subagent by the thrifty orchestrator.

0
installs
▌
Thrifty Dispatch · 2389-research bundle
Lean tiered-build orchestrator (JSONL-dispatch architecture). Use for "thrifty fast / lean / dispatch", or a multi-sprint build where cost matters. The architect (Sonnet) writes a contract + a sprints.jsonl and calls a dispatch SCRIPT that loops cheap bare model calls (claude -p --bare, subscription, no API key) to write each sprint to disk — NO subagents. The orchestrator never ingests sprint outputs, only a manifest, so its context stays tiny. Then it runs the gate and surgical-fixes.

0
installs
▌
Documentation Audit · 2389-research bundle
This skill should be used when verifying documentation claims against codebase reality. Triggers on "audit docs", "verify documentation", "check docs", "docs accurate", "documentation drift", "before release", "after refactor", "docs don't match". Uses two-pass extraction with pattern expansion for comprehensive detection.

0
installs
▌
Jam · 2389-research bundle
Structured multi-approach exploration using parallel perspective panels to generate, implement, and evaluate distinct variants, then synthesizes the best insights from all into the winner. Use when multiple approaches are genuinely viable and the choice is unclear, the user is indecisive or explicitly wants diverse perspectives, or the user says "jam on", "let's jam", or "jam session".

0
installs
▌
Landing Page Design · 2389-research
Create high-converting, visually distinctive landing pages. Use when building marketing pages, product launches, SaaS homepages, or any single-page conversion-focused website. Guides section-by-section composition with anti-AI-slop principles.

0
installs
▌
Sift Codebase Audit · 2389-research bundle
Use when asked to run SIFT (Structural Inspection for Technical Simplification), audit a codebase for simplification or refactoring opportunities, review structural complexity or tech debt, find invalid-state representations, or produce a prioritized simplification plan. A read-only, whole-repository audit covering data structures, state representation, control flow, algorithms, schemas, lifecycle/concurrency, and ownership boundaries. Not for single-file or diff-scoped reviews; recommends but never applies changes.

0
installs
▌
Terminal Title · 2389-research bundle
MANDATORY at session start. REQUIRED when user topic shifts (debugging to docs, frontend to backend, new subject, different component). The agent MUST invoke on all topic changes.

0
installs
▌
Trace · 2389-research bundle
Use when verifying a repository against its authoritative spec — spec-to-code audits, implementation-completeness reviews, release verification, behavior inventories, repo-wide acceptance testing, or when asked whether every documented requirement is implemented and actually works.

0
installs

43 published skills