Results for “design-document”

Design and deploy Salesforce restriction rules to subtract record access from users, covering eligibility, criteria syntax, metadata shape, and documented enforcement gaps.

Ensure .NET/C# code meets project-specific best practices for structure, design patterns, dependency injection, async/await, testing, configuration, and security.

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

Defines RESTful API design conventions including URL structure, status codes, error formats, pagination, versioning, rate limiting, CORS, validation, and OpenAPI documentation.

Drafts a state-compliant Last Will and Testament covering declarations, revocation of prior instruments, specific bequests, residuary disposition, guardian nominations, fiduciary appointments, and execution formalities. Conducts structured intake on family structure, asset inventory, fiduciary nominees, and existing estate plan documents. Coordinates with trusts, beneficiary designations, and non-probate transfers. Use when drafting wills, testamentary documents, pour-over wills, codicils, or estate planning instruments involving testamentary dispositions.

Establishes or validates a canonical Icon wrapper component, size token scale, stroke weight conventions, and illustration usage standards for a project, creating src/components/ui/icon.tsx and documenting the system.

Use this skill when the user asks how to design or improve a fleet safety scorecard — what KPIs to track, how to weight them, telematics signals vs document compliance vs roadside outcomes, monthly cadence, driver-facing vs admin-facing dashboards, gamification considerations, peer-comparison metrics, and how a scorecard ties to insurance premiums + retention. Reference SMS Methodology v3.20 for industry-standard weights.

Turn a design or spec document into a working MVP by planning thin vertical slices, scaffolding the first slice, then building iteratively with test-driven development and gated commits.

C++-specific library development patterns. Use when creating C++ libraries, designing header-only vs compiled libraries, configuring CMake for library targets, managing ABI stability and versioning, integrating with Conan/vcpkg, documenting with Doxygen, or testing with GoogleTest/Catch2. Extends meta-library-dev with C++ tooling and idioms.

Analyze and automatically remediate MoonSpec artifact inconsistencies across spec.md, plan.md, tasks.md, and related design files. Use when the user asks to run `/moonspec.align`, identify uncertainty, weigh tradeoffs in project context, edit artifacts without asking follow-up questions, resolve coverage gaps, or align generated MoonSpec documents before implementation.