Results for “patterns”

Create professional, visually polished GitHub README files with badges, diagrams, structured sections, and modern markdown design patterns. Use when creating or redesigning a repo's README for maximum GitHub impact.

Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.

Analyzes codebases to generate detailed technology stack blueprints with version information, licensing, usage patterns, coding conventions, and architecture diagrams.

Design REST and GraphQL APIs with OpenAPI 3.1 specifications, resource modeling, versioning strategies, pagination patterns, and error handling standards.

Guides the process of deprecating old systems, APIs, or features and migrating users to replacements, including decision frameworks, migration patterns, and removal strategies.

Analyzes project folder structures, auto-detects technology stacks, and generates detailed blueprints with naming conventions, file placement patterns, and templates for consistent code organization.

Analyzes smart contract codebases against Trail of Bits' secure development guidelines, generating documentation, reviewing architecture and upgradeability patterns, assessing implementation quality, identifying pitfalls, and providing prioritized recommendations.

Provides paragraph-level structural blueprints for writing systems papers targeting OSDI, SOSP, ASPLOS, NSDI, and EuroSys, including page allocation, writing patterns, and venue-specific checklists.

Learn Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.

Analyzes .NET project code coverage and CRAP (Change Risk Anti-Patterns) scores to identify risk hotspots, methods blocking coverage gains, and prioritize where to add tests.

Detects and removes AI writing patterns from Chinese text, making it sound more natural and human-like. Based on Wikipedia's comprehensive guide to AI writing characteristics.

HASH error handling patterns using error-stack crate. Use when working with Result types, Report types, defining custom errors, propagating errors with change_context, adding context with attach, implementing Error trait, or documenting error conditions in Rust code.

Analyzes Mintlify's design system, documenting its dual-mode aesthetic of atmospheric marketing heroes and dense developer documentation surfaces, including color tokens, typography hierarchy, and layout patterns.

Go-specific library/package development patterns. Use when creating Go libraries, designing public APIs with Go idioms, configuring go.mod, managing module versioning, publishing packages, or writing package documentation. Extends meta-library-dev with Go tooling and ecosystem practices.

Turns any long-running domain (business, relationships, health, career, learning, investing) into a local knowledge project with four layers, source tags, immutable snapshots, and a concept library that learns patterns over time.

Provides file paths to language-specific reference files for polyglot test analysis skills, enabling framework-aware detection of test markers, assertions, and patterns across .NET, Python, TypeScript, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, and C++.

Documents, standardizes, and governs a Vue 3 + shadcn-vue design system, including component documentation templates, patterns for forms, empty states, loading states, and feedback, plus a consistency checklist and conventional commit conventions.

Document architectural decisions in standardized ADR format. This skill should be used when making significant technical decisions, choosing between approaches, establishing patterns, or when other skills (create-plan, implement-plan, brainstorm) identify decisions that need documentation. Triggers on "document decision", "create ADR", "architectural decision", or automatically when invoked by other skills during planning and implementation.

Generate or improve MATLAB help text (documentation comments) for a function, class, or script file following MathWorks standards (H1 line, syntax paragraphs, See Also, 75-char lines). Read BEFORE writing MATLAB help — default patterns (Inputs:/Outputs: lists, block comments, uppercase See Also) produce non-conforming output. Use when writing, rewriting, fixing, or reviewing MATLAB help comments or function documentation.

Remove signs of AI-generated writing from academic medical papers. Use when editing or reviewing manuscripts to make them sound more natural and professionally written. Based on Wikipedia's "Signs of AI writing" guide, adapted for medical literature. Detects and fixes patterns including: inflated significance claims, superficial -ing analyses, vague attributions, AI vocabulary words, copula avoidance, excessive hedging, generic conclusions, informal word choices (linked/beyond/via/where/yield), overly assertive causal claims, and artificially condensed expressions. Preserves legitimate academic transitions (Notably, Prior studies have shown, etc.).

Performs deep architectural analysis of a specified module, directory, or feature area by examining structural coupling, data flow, concurrency patterns, risk, and SOLID alignment. Use when the user wants to assess, evaluate, or review the architecture, design quality, dependency structure, coupling, cohesion, or technical debt of an existing part of the codebase. Not for investigating specific bugs, runtime errors, or failures — use investigate. Not for test planning — use automated-test-planning. Not for file-level code review — use code-review. Not for researching open-ended options, prior art, or how something works — use research. Not for designing a new interface or contract — use design-an-api. Not for writing documentation or architectural decision records.