2K skills · sorted by relevance
Review a design system for inconsistent names and hardcoded visual values, document component variants and accessibility behavior, or propose new interface patterns that follow existing rules. Produce structured audits, component references, and design proposals.
Design and maintain applications where OpenRig agents help run the system. Organize instructions, shared state, and artifact checks, then trace unexpected behavior to the code, skill, or schema that needs repair.
Plan and verify OpenRig startup, shutdown, and recovery. Compare reported status with actual running sessions, distinguish recovery outcomes, and define reboot tests that expose partial failures instead of hiding them behind a fresh launch.
Classify agent work as ready to continue, needing human judgment, or intentionally paused. Structure decision requests with evidence, a recommended choice, and clear outcomes, then connect the recorded decision to the next responsible agent.
Review how an AI agent loads, retains, summarizes, and shares working information. This historical guide helps examine forgotten constraints, repeated actions, tool selection, and handoffs using context engineering practices published in 2024–2025.
Design an OpenRig agent team around a project goal. Create team and agent specifications, role guidance, and collaboration rules, then validate the setup and diagnose problems with startup instructions or agent coordination.
Guides the design and review of agent startup context, including role files and links to authoritative records. It helps identify stale guidance, missing updates, overloaded startup files, and instructions that lose the purpose of the work.
Apply a specific set of Rails conventions to design, implementation, and code review. It keeps business logic in models, represents state changes as records, limits dependencies, and uses Minitest with fixtures, or predefined test data.
Turn a recurring workflow into a new agent skill through guided discussion. Define use cases, activation conditions, file structure, and instructions, then create and validate SKILL.md and supporting files, including workflows using external tools through MCP.
Refactor React components that have too many true-or-false settings into reusable, flexible parts. This skill guides component composition, shared state, and API design, with examples and separate guidance for React 19 features.
Design appointment-based service websites with calm photography, spacious layouts, and clear treatment comparisons. Carry the same visual style through location, practitioner, and time selection, including booking confirmation, validation errors, retries, and preserved choices.
Design or review Apache Hudi tables through questions about data volume, updates, and usage. Get architecture recommendations, a decision record explaining tradeoffs, and configuration artifacts for supported processing paths.
Plan task handoffs between agents on different machines using Git to share YAML task and result files. This implementation specification describes validation, execution limits, result reporting, and GitHub Issues as an additional route for urgent requests.
Design amino acid sequences from a protein backbone stored in a PDB file using ProteinMPNN. Generate multiple candidates, redesign selected chains while preserving specified residues, and vary sampling settings to prepare sequences for downstream structure prediction.
Design amino acid sequences from a protein backbone using SolubleMPNN, a model trained on soluble protein structures. Generate candidates with a solubility bias for redesigning aggregation-prone proteins or preparing an E. coli expression screen.
Build TypeScript applications with consistent types across frontend and backend. Get help designing reusable types, checking values with type guards, configuring the compiler, and improving builds, with code and explanations of design choices.
Refactor React components that have accumulated many boolean options. Apply component composition, meaning building interfaces from cooperating parts, and shared state patterns to design reusable component libraries and clearer APIs, with guidance specific to React 19.
Improve APM CLI commands, help text, setup flows, and error messages. The skill checks consistency with familiar developer tools and guides wording so users understand failures and know what action to take next.
Refactor React components into reusable pieces with clearer interfaces. Provides patterns for replacing excessive boolean settings, sharing state through providers, and designing component libraries, with additional guidance for React 19 APIs.
Design and improve prompts and structured responses for AI applications. The skill also guides evaluation, retrieval augmented generation, which uses retrieved material to inform answers, and agent architecture, with references and scripts for production workflows.
Estimate intervention effects from existing data using causal analysis methods. Set up models, compare observed outcomes with estimates of what would have happened without intervention, check robustness, and interpret fitted results.
Defensive Golang coding against accidental bugs — nil panics, typed-nil interfaces, `append` backing-array aliasing, silent int64-to-int32 truncation, float `==` comparison, `defer` inside loops, defensive copies of slices and maps, and usable zero values. Use when a Go program panics on a nil map write or nil pointer dereference, when reviewing code for nil-safety, numeric conversion overflow, or resource lifecycle, or when designing a type whose zero value must be safe. Not for designing concurrent access with goroutines, channels, or sync primitives (→ See `samber/cc-skills-golang@golang-concurrency` skill), not for exploitable vulnerabilities such as injection, weak crypto, or leaked secrets (→ See `samber/cc-skills-golang@golang-security` skill), and not for debugging an already-failing program (→ See `samber/cc-skills-golang@golang-troubleshooting` skill).
The English summary is being prepared. Showing the original description.
Apply Martin Kleppmann-inspired data-system rules when designing reliability, scalability, consistency, replication, transactions, streams, or schema evolution.
The English summary is being prepared. Showing the original description.
Designs software architecture and selects appropriate patterns for projects. Use when designing systems, choosing architecture patterns, structuring projects, making technical decisions, or when asked about microservices, monoliths, or architectural approaches.
The English summary is being prepared. Showing the original description.