1arley-skills

Plugin 1arley-skills from marketplace 1arley in 1arley/skills. Commands read from the repo's manifest — 6 days ago.

Skills (19)

• code-review

  Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them s

• decision-to-adr

  Turns a decision record into numbered, provenance-preserving ADRs and an index. Use when the user asks to publish decisions as ADRs, write ADRs from the grill session, generate an ADR, document architecture decisions, or convert decision-record.md to docs/adr.

• feature-orchestrator

  Coordinate nontrivial software feature delivery through scoped agent stages, choosing cascade, incremental, prototype, risk-driven spiral, or formal-methods workflows. Use when implementation needs staged planning and delegation.

• rails-architecture

  Use when deciding where code belongs in a Rails app, when adding a service or model behavior, or when a controller is growing. Covers fat-model-thin-controller without the God object trap, when to extract a service, POROs vs ActiveRecord, and background jobs.

• rails-performance

  Use when a Rails page or endpoint is slow, when writing a query, or when reviewing code that touches the database in a loop. Covers N+1 detection, counter caches, includes vs preload vs eager_load, batching, pagination, and the caching layers.

• remotion-explainer

  Cria animações explicativas em Remotion (React + TypeScript) a partir de uma explicação técnica, com piloto, design system, variações, sincronia com narração e render para DaVinci Resolve. Use quando o usuário pedir animação explicativa, diagrama animado, cena de vídeo educativo, motion graphics pro

• ruby-style

  Use when writing or reviewing Ruby code, or when a style question comes up. Covers idiom, naming, method structure, exceptions, and collections - plus the cases where mainstream style guides disagree with each other and how to resolve the conflict.

• ruby-testing

  Use when writing or debugging tests in a Ruby project - RSpec or Minitest. Covers test design, factories vs fixtures, isolation, the shared-state traps that cause order-dependent failures, and how to debug a test that fails for a non-obvious reason.

• rust-architecture

  Place Rust code at useful crate and module boundaries, design public APIs, handle errors, and evaluate runtime or unsafe choices. Use when a change affects structure or long-term interfaces, not for routine local edits.

• rust-performance

  Investigate or improve Rust performance with measurement first. Use for profiling CPU, allocations, memory, latency, throughput, or async overhead; do not apply micro-optimizations without evidence.

• rust-style

  Write or review idiomatic Rust by following the repository's conventions for ownership, errors, naming, documentation, formatting, and linting. Use for general Rust code; use focused async or unsafe guidance when those are central.

• rust-testing

  Design, add, or diagnose Rust tests using the repository's existing test structure and tools. Covers unit, integration, documentation, async, and property-oriented tests without assuming a particular test framework.

• scoped-git-workflow

  Create semi-granular, scope-preserving Conventional Commits and push them to the current Git remote when the user asks to commit and push code changes.

• laws-of-ui

  Audit existing web pages from live interfaces, screenshots, prototypes, or source code, and plan new pages with practical guidance grounded in Laws of UI. Use for UI critiques, redesigns, and page specifications; not general code review.

• laws-of-ux

  Audit existing web pages and plan new ones with practical UX guidance grounded in Laws of UX, task evidence, and accessible interaction. Use for UX reviews, page planning, or redesigns.

• llm-cost-guard

  Estimate cost LLM call, set spending cap, budget API calls, how much will cost, track token usage, stop if costs more than. Use before any paid LLM call when user asks to estimate or cap spending.

• skill-preflight

  Audits a skill folder for format, structure, static security, and supply-chain issues. Use when someone says “audit this skill”, “check my SKILL.md”, “is this skill safe to publish”, “lint skill”, or “prepare for marketplace”.

• ui-component-scout

  Find and evaluate free UI components for existing-page audits and new web pages. Use for component research, UI audits, accessibility or performance improvements, and page planning across React, Vue, Svelte, Angular, HTML, and Tailwind projects. Uses Tailkits for discovery and verifies details with

• grill-with-jev

  Grill a plan or design in rounds where JEV, the user's automated stand-in, decides through schema-validated answers. Use only when explicitly invoked.

Similar plugins