Architecture & codebase
12,711 rows, by stacks then stars
1,011 of these skill files have been read, by 858 distinct authors, and what they tell an agent counted. What Architecture & codebase authors agree on, and what they forbid
yigityildiz0/universal-ai-skill-library/skills/common/project-layout-refactor Skill
no license1★ repoAudit and safely refactor a repository's directory layout while preserving behavior, imports, build tooling, history, generated-file rules, and user.
yigityildiz0/universal-ai-skill-library/skills/common/refactor-plan Skill
no license1★ repoPlan a multi-file refactor with proper sequencing and rollback steps
yigityildiz0/universal-ai-skill-library/skills/common/refactor Skill
no license1★ repoSurgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god.
yigityildiz0/universal-ai-skill-library/skills/common/refactoring-expert Skill
no license1★ repoSafe code refactoring using proven patterns from Martin Fowler's catalog. Use when restructuring code, extracting methods/classes, simplifying conditionals.
yigityildiz0/universal-ai-skill-library/skills/common/renaissance-architecture Skill
no license1★ repoSoftware architecture and UI/UX principles for building genuinely new solutions, not derivative work. Use when designing features, architecting software.
yigityildiz0/universal-ai-skill-library/skills/common/setup-writing-style Skill
no license1★ repoBuild a private, evidence-based writing-style profile from text the user explicitly provides, then calibrate it against drafts without copying distinctive passages or silently persisting personal data. Use when the user asks to capture their voice or make drafts sound like them; never scan unrelated messages, email, or files automatically.
yigityildiz0/universal-ai-skill-library/skills/common/technical-debt-analyzer Skill
no license1★ repoQuantify, categorize, and prioritize technical debt using SQALE methodology with interest calculation and remediation planning. Use when assessing code.
yigityildiz0/universal-ai-skill-library/skills/common/test-structure Skill
no license1★ repoSet up testing infrastructure including framework selection, directory organization, configuration files, and initial test scaffolding. Use when starting a.
yigityildiz0/universal-ai-skill-library/skills/common/version-upgrade Skill
no license1★ repoSafely plan and apply a project release version bump with ecosystem-aware file discovery, previewed diffs, changelog evidence, validation, and rollback. Use.
yigityildiz0/universal-ai-skill-library/skills/common/xcode-project-setup Skill
no license1★ repoSafely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g..
M0rtalPhe0nix/dotfiles/.agents/skills/codebase-design Skill
1★ repoShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
The same file is in 19 other repositories
M0rtalPhe0nix/dotfiles/.agents/skills/improve-codebase-architecture Skill
1★ repoScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
The same file is in 8 other repositories
M0rtalPhe0nix/dotfiles/.agents/skills/request-refactor-plan Skill
1★ repoCreate a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
The same file is in 13 other repositories
M0rtalPhe0nix/dotfiles/.agents/skills/setup-matt-pocock-skills Skill
1★ repoConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
The same file is in 6 other repositories
M0rtalPhe0nix/dotfiles/.agents/skills/setup-pre-commit Skill
1★ repoSet up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
The same file is in 19 other repositories
M0rtalPhe0nix/dotfiles/.claude/skills/compare-dotfiles Skill
1★ repoCompare the GitHub default branch of M0rtalPhe0nix/dotfiles with one user-supplied public GitHub dotfiles repository and produce an evidence-backed improvement backlog. Use when the user wants to compare dotfiles, discover missing features, find stronger implementations or clever configuration tricks, or gather inspiration from another public dotfiles repository.
jpbaking/agentic-tests/skills/shared/agentic-refactor Skill
1★ repoRefactor or optimize main code while the agent-test suite (and user tests) must stay green after every change. The inverse of agentic-unit-test — main code may change, tests may not. Use when asked to refactor, optimize, or clean up code that agent tests already lock down.
nguyenthdat/opencode-manager/registry/skills/codebase-design Skill
1★ repoModule-level design vocabulary and decision process for deep interfaces, seam placement, dependency direction, and module decomposition. Use when designing a new module/package/crate/namespace, evaluating an existing module's depth and testability, placing a seam between units that vary independently, reviewing dependency graphs for cycles or leaky abstractions, or designing cross-language FFI boundaries in multi-language repositories. Covers Rust, TypeScript, Python, Go, C#, Kotlin, Java, C, C++, Swift, Objective-C, Zig, Lua, Ruby, PHP, JavaScript, Groovy, PowerShell, Bash, Assembly, and any language pair for FFI interop. Do not use for system-level architecture decisions (see `software-architect`) or code-level pattern selection (see `design-patterns`).
nguyenthdat/opencode-manager/registry/skills/design-patterns Skill
1★ repoLanguage-agnostic design-pattern selection and implementation for architecture, refactors, reusable abstractions, runtime polymorphism, factories/builders, wrappers, state machines, commands, observers, and other GoF and modern architectural patterns. Applies whenever a non-trivial design in Rust, TypeScript, Python, Go, C#, Kotlin, C, C++, Swift, or any other language needs a pattern decision, or when reviewing pattern-heavy code. Prefer idiomatic native constructs and simpler concrete code first; do not use for naming a pattern without real design pressure.
nguyenthdat/opencode-manager/registry/skills/software-architect Skill
1★ repoUse when making or reviewing a system/service-level architecture decision: choosing an architecture style, recording an ADR, evaluating build-vs-buy, defining service/data boundaries, or designing failure-mode/resilience strategy across services. Do not use for in-module interface design (see `codebase-design`) or code-level GoF pattern selection (see `design-patterns`).
zdnemz/claude-team/.claude/skills/initialize-project Skill
1★ repoInitialize the autonomous agent system from docs/proposal.md — interview the user, generate specs and legend→epic→story→task plans, assemble the project-specific team, set state to PLANNED. Use when state phase is UNINITIALIZED (or resuming INITIALIZING) and docs/proposal.md exists.
LeonardSEO/power-platform-skills-codex/plugins/mobile-app/skills/setup-datamodel Skill
1★ repoUse when the user wants to design or redesign the Dataverse schema and connector plan for an existing mobile app, or has an ER diagram (image, Mermaid, or text) to apply. Skip when the user is creating a brand-new app — /create-mobile-app handles the data model inline.
The same file is in 1 other repository
LeonardSEO/power-platform-skills-codex/plugins/mobile-app/skills/setup-offline-profile Skill
1★ repoUse when the user wants to enable offline mode for a Power Apps mobile app and create a Mobile Offline Profile in Dataverse — designs per-table row scope, relationships, columns, and sync frequency through a 3-gate approval flow.
The same file is in 1 other repository
LeonardSEO/power-platform-skills-codex/plugins/power-automate/skills/setup Skill
1★ repoSet up Power Automate CLI prerequisites. Use when the user is new, something isn't working, or they need help getting started.
The same file is in 1 other repository
LeonardSEO/power-platform-skills-codex/plugins/power-pages/skills/create-site Skill
1★ repoCreates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new Power Pages website or portal.
The same file is in 1 other repository
LeonardSEO/power-platform-skills-codex/plugins/power-pages/skills/setup-auth Skill
1★ repoUse when the user asks to "set up authentication", "add login", "add logout", "add sign in", "enable auth", "add role-based access", "add authorization", "protect routes", "configure identity provider", "configure Entra ID", "configure Entra External ID", "configure OpenID Connect", "add OIDC", "set up SAML", "set up WS-Federation", "set up local login", "add Facebook login", "add Google sign in", "add Microsoft Account", or otherwise wants to set up authentication (login/logout) and role-based authorization for their Power Pages code site using any supported identity provider. Also sets up the IdP app registration for OIDC providers (Okta, Auth0, Entra External ID, and other OIDC) -- reads the provider's docs first, then either guides the user through the provider's console or, when the provider supports it, configures it for the user -- and wires the client ID, authority, and claims mapping into Power Pages.
The same file is in 1 other repository
LeonardSEO/power-platform-skills-codex/plugins/power-pages/skills/setup-datamodel Skill
1★ repoCreates Dataverse tables, columns, and relationships for a Power Pages site based on a data model proposal. Use when the user wants to set up the data model, create database tables, or build the Dataverse schema for their site.
The same file is in 1 other repository
LeonardSEO/power-platform-skills-codex/plugins/power-pages/skills/setup-pipeline Skill
1★ repoSets up a Power Platform Pipeline for automated Power Pages deployments. Power Platform Pipelines is Microsoft's native CI/CD tool built into the Power Platform — no external infrastructure required. Use when asked to: "set up ci/cd", "create pipeline", "setup pipeline", "set up power platform pipelines", "create power pipelines", "automate deployments", "set up automated deployment", "create deployment pipeline", "use power pipelines". Also handles: "set up github actions" or "set up azure devops pipeline" (shows coming-soon guidance for those platforms).
The same file is in 1 other repository
LeonardSEO/power-platform-skills-codex/plugins/power-pages/skills/setup-solution Skill
1★ repoCreates a Dataverse publisher and solution, then adds Power Pages site components to the solution for ALM and deployment management. Use when asked to: "create solution", "set up solution", "add to solution", "package site into solution", "create publisher", "solutionize my site", or "set up ALM for my site".
The same file is in 1 other repository
mohamedzhioua/proofguard/skills/clean-diff-guard Skill
1★ repoKeeps a diff surgical and scoped — blocks unrelated file edits, whole-file/whole-repo formatter sweeps, over-engineered abstractions for a small ask, leftover debug/dead code, and overwriting the user's uncommitted work. Best used reactively before presenting or committing a code change, when files were edited, generated, moved, deleted, or reformatted. Use when the user says "make the change", "fix this", "refactor", "commit", or after a coding agent edits files. DO NOT USE for test-code quality (out of proofguard's scope; a test-quality-guard is in `deferred/`, not yet shipped), doc sync (docs-drift-guard), or the final done-claim (evidence-before-done); this guard keeps the DIFF surgical and scoped.
jahfaliabdulrahman-dev/hermes-skills/skills/flutter-isar-clean-arch-setup Skill
1★ repoSet up a Flutter + Isar + Riverpod Clean Architecture project. Covers manual file creation, schema generation, avoiding dependency hell, and structuring domain/data/presentation layers.
cskwork/supermarketer-skill/vendor/marketingskills/skills/onboarding Skill
1★ repoWhen the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails.
The same file is in 3 other repositories
cskwork/supermarketer-skill/vendor/marketingskills/skills/site-architecture Skill
1★ repoWhen the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.
The same file is in 5 other repositories
kfeng209-oss/cognitive-ux/skills/cognitive-ux-onboarding Skill
1★ repoDesign and audit first-run, activation, setup, and guided onboarding experiences using evidence-informed UX. Use when a new user must reach initial value in a product; return a time-to-value map, progressive setup, permission and data-request disclosure, empty-state design, recovery paths, accessibility checks, and activation-quality metrics.
yinyoudexing/skill-compass/examples/demo-skills/project-onboarding Skill
1★ repoUse when documenting an unfamiliar repository and creating repeatable setup and verification steps
jpoindexter/ux-flow-skills/skills/flow-onboarding Skill
1★ repoUse when designing or reviewing onboarding, first-run, welcome, setup-wizard, or activation flows — new-user signup-to-first-value paths, personalization quizzes, product tours, or getting-started checklists. Also use when metrics show drop-off between signup and first key action, users report 'I signed up but didn't know what to do', or an app opens to a blank screen for new users.
vivekkhimani/gtm-tools-template/.agents/skills/gtm-setup Skill
1★ repoOnboarding skill — walks a new user through installation, API key configuration, PhantomBuster agent IDs, first client setup (auto-research from domain + 5 refinement questions), and a skill tour. Run this first after cloning the repo. Also triggers on "set up gtm skills", "configure gtm", "gtm onboarding", "first time setup".
ssdiwu/507-skills/code/507-inspect Skill
1★ repo不围绕某次交付 diff,只读检查代码库的模块形状、接缝与架构摩擦,产出证据候选报告交给 507-simplify。Use when user says 架构审查, 代码体检, 找重构机会, 浅模块改深, 找接缝, inspect architecture, codebase architecture review, refactor opportunity. 明确变更范围的交付 review 使用 507-review。
ssdiwu/507-skills/code/507-setup Skill
1★ repo为一个或多个代码项目做工作流初始化或全量规范巡检:核对 AGENTS、README、CHANGELOG、doc、术语、决策和代码目录现实,先报告再路由。Use when user says 项目初始化, 项目规范巡检, 工作流初始化, 校准 AGENTS, project setup, project bootstrap, scaffold. 不用于代码体检或架构 review;专项地图维护使用 507-map。
ssdiwu/507-skills/code/507-simplify Skill
1★ repo在保持公开契约与可观察行为不变的前提下,对指定代码范围或 507-inspect 报告逐项建立证据、修改并验证。可深入内部模块、抽象与接缝;若需要行为变化则停止并路由到需求实施。Use when user mentions simplify, simplify code, 简化, 简化代码, 行为不变重构, 内部简化, 按报告修改, 处理 inspect 报告, 局部重构, 降低复杂度, 收敛架构摩擦。
andr-ca/agentharness/.claude/skills/api-design Skill
1★ repoUse when designing, reviewing, or evolving a REST or GraphQL API — resource naming, HTTP status codes, versioning strategy, error response shapes, pagination, and authentication patterns.
andr-ca/agentharness/.claude/skills/clean-architecture Skill
1★ repoUse when business logic is entangled with frameworks or databases. Covers hexagonal architecture (ports and adapters), layer diagram, dependency direction rules, and violation symptoms.
andr-ca/agentharness/.claude/skills/port-agent-config Skill
1★ repoUse when asked to port, migrate, or add equivalent agent instructions, skills, or custom sub-agents for a different coding tool than the one already configured — e.g. "add Cursor support from our CLAUDE.md", "we're switching from Cursor to Codex, port our rules", "make this work for Copilot too", "port our review subagent to Codex". Covers both agentharness-linked projects (use the real generators, don't hand-write) and plain projects with hand-authored config (port by hand, same principles).
atlax-tech/harness-armor/skills/harness-init Skill
no license1★ repoCreate a fact-safe Harness Engineering skeleton for an empty or basic-files-only repository, including a short AGENTS.md, project document stubs, and managed state. Use when starting an undefined repository or explicitly invoking harness-init. Do not use when substantive product documents or business code already exist, and never guess the product or technology stack.
RudrenduPaul/evolveguard/fixtures/labeled-non-breaking-edits/case-03-add-write-capability/after Skill
1★ repoScans a monorepo, reports a dependency inventory, and caches results to disk.
RudrenduPaul/evolveguard/fixtures/labeled-non-breaking-edits/case-03-add-write-capability/before Skill
1★ repoScans a monorepo and reports a dependency inventory.
giacomoguidotto/skills/skills/setup-agentic-os Skill
1★ repo🧩 Curated, auditable agent skills for knowledge, mastery, career, and cross-system orchestration.
The same file is in 1 other repository
giacomoguidotto/skills/skills/setup-career-system Skill
1★ repoCheck or reconcile a standalone Career System checkout through its canonical versioned gateway.
The same file is in 1 other repository
giacomoguidotto/skills/skills/setup-knowledge-system Skill
1★ repoCheck or reconcile the standalone Knowledge System. Use when the user invokes /setup-knowledge-system, or asks to install, update, health-check, or reconcile Knowledge System bindings, public skills, the shared interface package, or KB Reconcile.
The same file is in 2 other repositories
giacomoguidotto/skills/skills/setup-mastery-system Skill
1★ repoCheck or reconcile the independently usable Mastery System repository and its GitHub issue-tracker prerequisites.
The same file is in 2 other repositories
Paldom/node-skills/skills/nextjs-quality Skill
1★ repoTunes Next.js App Router application quality - next.config hardening, eslint-config-next flat config, strict mode and typed routes, RSC and use-client boundary hygiene, bundle analysis, image and font optimization. Use when the user asks to production-harden a Next.js app, fix hydration or use-client errors, or shrink a Next bundle. Not for generic Node linting, unit test setup, or npm packaging.
Paldom/node-skills/skills/node-lint Skill
1★ repoSets up and tunes linting and formatting for Node/TypeScript projects - Biome as the one-tool option or ESLint flat config plus Prettier, rule tuning, eslintrc-to-flat and ESLint-to-Biome migrations, editor and CI wiring. Use when the user asks to set up or fix linting, formatting, ESLint, Biome, or Prettier. Not for Next.js apps, type checking, or test setup.
Paldom/node-skills/skills/node-testing Skill
1★ repoBuilds unit and integration test infrastructure for Node/TS/React - Vitest or node:test selection with explicit config, v8 coverage gates that fail CI, React Testing Library, mocking discipline, flaky-test triage. Use when the user asks to set up tests, add coverage thresholds, pick a test runner, or fix a flaky test setup. Not for E2E browser suites, lint rules, or CI workflow authoring.
dineshrevunuru/SuperSkills/codebase-design Skill
1★ repoThe deep-module vocabulary and heuristics for structuring the React/Next/TypeScript code Dinesh ships — a lot of behavior behind a small interface, placed at a clean seam, tested through that interface — so an ARIA sub-agent (or future-him) can navigate and safely edit a shipped app fast. Use when designing or restructuring a component/hook/module's interface, deciding where a seam goes, asking 'is this module too shallow?', 'should this be one module or three?', 'how do I make this testable / AI-navigable?', 'this wrapper adds nothing', or when another SHIP skill needs the deep-module language. Names things exactly — module, interface, depth, seam, adapter, leverage, locality — and runs the deletion test + the two-adapter rule. NOT for prototypes (throwaway code needs no seams — `build-coded-prototypes`); NOT a diff review (`review-shipped-code` flags a shallow module, this reshapes it).
dineshrevunuru/SuperSkills/improve-animations Skill
1★ repoSurvey a whole codebase's motion as a senior motion advisor, then produce a prioritized, register-aware audit and self-contained implementation plans other agents (including cheaper models) execute. READ-ONLY on source — it plans motion fixes, it never applies them. Use when the ask zooms OUT on the whole app's motion: 'improve the animations', 'audit the motion', 'the app feels janky/sluggish/cheap', 'where should the motion get better', 'make this feel more polished', or 'give me a roadmap of animation fixes' — not a verdict on one diff. Mirrors improve-code-architecture's scan→report→plan shape for motion.
dineshrevunuru/SuperSkills/improve-code-architecture Skill
1★ repoFind where a React/Next/TypeScript codebase has started to ROT, render the opportunities as a visual HTML report you can actually look at, then drill into the one you pick and scope its fix. The scan→report→drill shape for whole-codebase architecture — the SHIP-wing skill that zooms OUT, above a single diff (review-shipped-code) or a single bug (diagnose-bugs). Low-priority by design: only worth running once an app is big enough to rot. Use when a codebase 'is getting hard to work in', 'feels tangled', 'where should I refactor', 'scan for refactor opportunities', 'architecture review', 'this god-component is out of control', or one area keeps breeding bugs. NOT for young/small apps (nothing to deepen yet) or prototypes.
dineshrevunuru/SuperSkills/make-setup-wizard Skill
1★ repoGenerate an interactive bash WIZARD that walks a human step by step through a manual setup procedure — opening each URL, saying exactly what to click and copy, capturing values into `.env`, confirming at every stage, and blocking on a skipped step. Use when a repeated manual setup is tedious to re-explain — third-party service config, a one-off migration, an A→B state transition — or asked to 'turn these setup steps into a wizard', 'script this onboarding', 'make a guided setup', 'walk me through this env setup', 'automate this manual procedure', or 'generate a setup script'. The bash UX is already solved in `template.sh`; your job is to scope the procedure and author its stages. Defaults to a local `.env` + scratch path for solo work and wires GitHub Actions secrets only when the repo has real CI. A wizard is a CONTROL against a skipped step, not a reminder.
dineshrevunuru/SuperSkills/migrate-to-library Skill
1★ repoMove code from one library or API to a chosen replacement SAFELY — safety net first, migrate incrementally, green between each. Use when 'migrate off X to Y', 'replace this library', 'swap axios for fetch', 'move from lodash to native', 'port this to the new SDK', 'deprecate this dependency', 'we're switching from X to Y', 'codemod this', or a dependency is EOL/deprecated and callers must move. Mode-switches: scrappy compiler-checked rename for a pure API swap; rigor characterization-net-first the moment runtime behavior can drift (data-fetch, dates, validation, state). Solo by default — tracks remaining call sites in a local grep-driven checklist, not a team tracker; mode-switches UP to issues only when one actually exists. NOT for restructuring internal code without swapping a dependency (`improve-code-architecture`) or building new from a spec (`implement-spec`).
dineshrevunuru/SuperSkills/plan-refactor Skill
1★ repoPlan a behavior-preserving refactor BEFORE touching it: fix the target shape, name the regression risk, pin behavior at the seam, then sequence it into small **always-green** steps that avoid a **big-bang rewrite**. Use when 'just clean this up', 'refactor X', 'this file is a mess', 'untangle this module', 'restructure this before I add to it', or before reshaping a risky area you don't want to break. SOLO DEFAULT: presents the plan / writes a local `refactor-plan.md` — mode-switches UP to a tracker issue only when Dinesh runs one. NOT for finding WHERE to refactor across an app (improve-code-architecture), the target module shape itself (codebase-design), or slicing NEW feature work (plan-work-tickets).
dineshrevunuru/SuperSkills/scaffold-practice-project Skill
1★ repoScaffold a small buildable practice project — a green-running baseline with one deliberate gap — to learn a concept by BUILDING it, not reading about it. Use when Dinesh says 'let me build a tiny thing to learn X', 'scaffold a practice repo/sandbox', 'set up a project to try Y', 'I learn this by making it', 'give me a failing test to implement', 'stub out an exercise for this pattern', or when a teach-me lesson needs its build-to-learn artifact stood up. Generalizes course-exercise scaffolding (problem/solution/reference split, one-command run, a red baseline you turn green) to any solo React/Next/TypeScript practice repo — defaults to a single throwaway file and mode-switches up to a minimal framework repo only when the framework IS the concept.