turborepo
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI…
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 11-14 00:15
40,999 results
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI…
MUST be used for Vue.js tasks. Strongly recommends Composition API with `<script setup>` and TypeScript as the standard approach. Covers Vue 3, SSR, Volar,…
Single Source of Truth (SSOT) guidelines for SwiftUI state management. Use when designing state architecture, choosing between…
Use skill if you are building, modernizing, or reviewing macOS SwiftUI code with Apple's Liquid Glass design system — glass toolbars, sidebars, windows,…
Maintain code comments that are easy to search and understand, supplementing interface contracts and implementation rationale.
Write Symfony console commands as thin translation layers over a service: one class per command family with method-level #[AsCommand] on Symfony 8.1, invokable…
Decide what happens to an uploaded file once the controller has it: public under public/ or protected behind a controller, Flysystem so local development and…
Recovery from git mistakes. Use when you need to undo commits, recover branches, or fix history.
Based on the methodology of learning-notes-organizer, perform a local refactoring workflow on the specified file: "full heading index + meaning/guidance annotations + refactoring of specified sections + routing out-of-bounds content to appropriate headings and adding to-be-organized containers as needed"; use planning-with-files to output extract → plan → map → deliver, with out-of-scope sections left unchanged by default and only the minimal changes required for migration.
Places app code in the src/ layout and checks import boundaries: one-way zones, pure core, ports with fakes, one composition root. Use when adding a file,…
Use for Agent Implement when taking one tracker issue through the full implementation pipeline by claiming the issue, making scoped changes locally or…
Use for code review before opening a PR, before handing off a branch, or when reviewing committed changes, uncommitted changes, a PR branch, or a main-branch…
Assess codebase architecture and propose module interface or ownership improvements from concrete caller and change-history evidence. Use for requested…
Diagnose bugs, failing tests, build failures, performance regressions, and unexpected behavior using reproductions and hypothesis tests. Use for debugging…
Add a new enforce(), check(), or guidance() rule to an existing spec file
Swift/SwiftUI strictness, clean code, and security rules. Use when writing, reviewing, or refactoring Swift code in iOS/macOS projects. Covers force unwrap…
Writes, reviews, and improves SwiftData code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use SwiftData.
Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI…
REST API design patterns, structure, and best practices. Use when user asks to "design a REST API", "create API endpoints", "write OpenAPI spec", "design API…
Check if a GitHub issue is a duplicate and find related issues and PRs.
Analyze a GitHub issue and provide a structured summary with next-action assessment.
Code walkthrough skill: helps quickly understand unfamiliar projects or modules and build a mental model. Organizes code layer by layer, progressing from overall architecture to core flows to key design decisions. It is not simply reading files and listing directories, but distilling "what this code is doing, why it does it this way, and how it connects to other parts."…
Dependency analysis skill: answers "what will be affected if I change this?" Traces call chains, data flow, and side effects, and assesses the impact scope of a change. Difference from code-walkthrough: walkthrough focuses on "what it is," while dependency-map focuses on "what changing it affects." Trigger words: impact scope, what will changing this affect, dependencies, call chain, impact analysis, who is using this.…
Structured process for large-scale refactoring: impact analysis -> building a safety net -> step-by-step refactoring -> regression verification. Suitable for non-trivial refactoring involving multiple files, architectural adjustments, module decoupling, interface redesign, etc. This skill is a process skill (orchestration type), reusing task-execute to manage progress, task-finish for wrap-up, dependency-map for impact analysis, writing...