dtsong
- 288 skills
- 0 followers
- last month last updated
- ▌ Failure Mode Analysis 3 · dtsongUse when systematically identifying failure scenarios for proposed features and infrastructure changes. Covers component enumeration, failure mode discovery, cascade analysis, mitigation design, monitoring signals, and rollback planning. Do not use for security threat modeling (use threat-model) or input boundary testing (use edge-case-enumeration).
- ▌ Threat Model 3 · dtsongUse when applying STRIDE threat modeling to identify security risks in proposed features. Covers trust boundary mapping, data flow analysis, threat rating, mitigation proposals, and residual risk documentation. Do not use for failure scenario discovery (use failure-mode-analysis) or boundary value testing (use edge-case-enumeration).
- ▌ Cost Analysis 3 · dtsongUse when modeling infrastructure costs, projecting scaling expenses, or identifying optimization opportunities across cloud providers and third-party services. Covers per-unit cost estimation, growth milestone projections, and budget alerting setup. Do not use for deployment strategy design (use deployment-plan) or monitoring architecture (use observability-design).
- ▌ Technology Radar 3 · dtsongUse when evaluating frameworks, tools, or platforms for adoption, migration, or stack decisions. Covers maturity assessment, ecosystem health, team readiness, migration cost, and long-term viability with radar quadrant placement. Do not use for comparing individual libraries (use library-evaluation) or analyzing competing products (use competitive-analysis).
- ▌ Mvp Scoping 3 · dtsongUse when defining minimum viable scope for a product or feature launch. Covers MoSCoW prioritization, value-effort matrix analysis, MVP cut-line definition, and phased roadmap planning. Do not use for quantified feature comparison (use impact-estimation) or measurement instrumentation (use analytics-design).
- ▌ Journey Mapping 3 · dtsongUse when mapping complete user journeys through multi-step flows, onboarding sequences, or feature workflows. Covers entry points, happy paths, alternate paths, error states, friction analysis, and delight opportunities. Do not use for individual component interaction specs (use interaction-design).
- ▌ Prompt Engineering 3 · dtsongUse when designing, evaluating, or versioning system prompts for LLM-powered features. Covers instruction structure, chain-of-thought patterns, output format constraints, few-shot example selection, and prompt versioning strategy. Do not use for RAG pipeline design (use rag-architecture) or AI evaluation frameworks (use ai-evaluation).
- ▌ Codebase Context 3 · dtsongUse when analyzing an existing codebase for architecture, tech stack, conventions, and infrastructure. Covers project structure mapping, data model discovery, integration point cataloging, and constraint identification. Do not use for schema changes (use schema-design) or API contract definition (use api-design).
- ▌ Pattern Analysis 3 · dtsongUse when auditing codebase patterns or evaluating proposed changes for convention consistency. Covers file naming, component patterns, data fetching, state management, and type conventions. Do not use for test plan design or coverage targets (use testing-strategy).
- ▌ Competitive Analysis 3 · dtsongUse when designing features that exist in competing products or analyzing prior art in the market. Covers feature mapping, UX evaluation, technical trade-off assessment, and differentiation opportunity identification. Do not use for evaluating individual libraries (use library-evaluation) or assessing technology maturity (use technology-radar).
- ▌ Interaction Design 3 · dtsongUse when designing component interaction specs with visual states, transitions, and accessibility requirements. Covers state matrices, responsive behavior, ARIA compliance, and content constraints. Do not use for multi-step user journey mapping (use journey-mapping).
- ▌ Data Classification 3 · dtsongUse when classifying data elements by sensitivity tier and defining per-tier handling requirements. Covers data inventory, sensitivity classification, PII flow mapping, encryption and masking specifications, and cross-boundary transfer documentation. Do not use for regulatory gap analysis (use compliance-review) or audit logging design (use audit-trail-design).
- ▌ Impact Estimation 3 · dtsongUse when comparing multiple features or initiatives to determine prioritization order. Covers RICE scoring with quantified reach, impact, confidence, and effort dimensions, tier ranking, and success metric definition. Do not use for MVP scope definition (use mvp-scoping) or analytics instrumentation planning (use analytics-design).
- ▌ Documentation Plan 3 · dtsongUse when designing documentation architecture for a project or team. Covers audience mapping, Diataxis framework classification, onboarding path design, format and location decisions, documentation testing, and maintenance scheduling. Do not use for recording individual architecture decisions (use adr-template) or creating versioned changelogs (use changelog-design).
- ▌ AI Evaluation 3 · dtsongUse when designing an evaluation framework for AI/LLM features. Covers golden dataset creation, automated scoring rubrics, hallucination detection, regression testing infrastructure, and production monitoring. Do not use for prompt design (use prompt-engineering) or RAG pipeline architecture (use rag-architecture).
- ▌ Git Status · dtsongQuick git queries - status, diff, log, blame. Triggers on "git status", "what changed", "show diff", "recent commits".
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Dbt Skill 2 · dtsong bundleUse when working with dbt (data build tool) - creating models, writing tests, CI/CD pipelines, materializations, sources, staging/intermediate/marts layers, Snowflake/BigQuery warehouse configuration, incremental strategies, Jinja macros, data quality, semantic layer, or making analytics engineering decisions
- ▌ Git Workflows 2 · dtsong bundleLocal git operations for syncing, branching, merging, and conflict resolution
- ▌ Prompt Wizard 2 · dtsongInteractive wizard to craft effective prompts using Claude Code best practices
- ▌ Github Workflow 2 · dtsong bundleGitHub interactions for issues, pull requests, releases, labels, and repository management via the gh CLI.
- ▌ Language Conventions 2 · dtsong bundleLanguage and project convention references for Python, TypeScript, and Terraform. Use when setting up new projects, reviewing code conventions, or ensuring consistency. Covers tooling, configs, patterns, testing, and project structure.
- ▌ Web Security Hardening 2 · dtsong bundleSecurity audit checklist for web applications. Use when reviewing, auditing, or hardening a web app's security posture. Covers rate limiting, auth headers, IP blocking, CORS, security middleware, input validation, file upload limits, ORM usage, and password hashing. Triggers on requests like "review security", "harden this app", "security audit", "check for vulnerabilities", or when building/reviewing API endpoints.
- ▌ Git Pull 2 · dtsongUse when pulling remote changes with an explicit merge or rebase strategy choice.
- ▌ Git Push 2 · dtsongUse when pushing commits to the remote, including first-push upstream tracking setup.
- ▌ Git Sync 2 · dtsongUse when fetching and reviewing remote changes without modifying the local branch state.
- ▌ QA Coordinator 2 · dtsongUse when a user reports a frontend bug, visual defect, or unexpected behavior in a Next.js/TypeScript application. Orchestrates a multi-phase QA pipeline — component mapping, diagnosis, fix, and regression testing — by classifying symptoms and dispatching to the appropriate specialist skill. Does not perform diagnosis or fixes directly; delegates all domain work to specialists. Not for backend-only issues, infrastructure problems, or build/deployment failures.
- ▌ Git Abort 2 · dtsongUse when a merge, rebase, or cherry-pick has gone wrong and needs to be safely aborted.
- ▌ Git Stash 2 · dtsongUse when saving, listing, applying, or dropping stashed changes during context switches.
- ▌ Git Branch 2 · dtsongUse when creating a new git branch following the project's branch naming conventions.
- ▌ Git Rebase 2 · dtsongUse when rebasing the current branch onto main with guidance through each step.
- ▌ Git Squash 2 · dtsongUse when squashing multiple commits non-interactively to produce a cleaner linear history.
- ▌ Git Switch 2 · dtsongUse when switching branches safely while handling uncommitted changes via stash or commit.
- ▌ AI Evaluation 2 · dtsongUse when designing an evaluation framework for AI/LLM features. Covers golden dataset creation, automated scoring rubrics, hallucination detection, regression testing infrastructure, and production monitoring. Do not use for prompt design (use prompt-engineering) or RAG pipeline architecture (use rag-architecture).
- ▌ Threat Model 2 · dtsongUse when applying STRIDE threat modeling to identify security risks in proposed features. Covers trust boundary mapping, data flow analysis, threat rating, mitigation proposals, and residual risk documentation. Do not use for failure scenario discovery (use failure-mode-analysis) or boundary value testing (use edge-case-enumeration).
- ▌ Cost Analysis 2 · dtsongUse when modeling infrastructure costs, projecting scaling expenses, or identifying optimization opportunities across cloud providers and third-party services. Covers per-unit cost estimation, growth milestone projections, and budget alerting setup. Do not use for deployment strategy design (use deployment-plan) or monitoring architecture (use observability-design).
- ▌ Technology Radar 2 · dtsongUse when evaluating frameworks, tools, or platforms for adoption, migration, or stack decisions. Covers maturity assessment, ecosystem health, team readiness, migration cost, and long-term viability with radar quadrant placement. Do not use for comparing individual libraries (use library-evaluation) or analyzing competing products (use competitive-analysis).
- ▌ Mvp Scoping 2 · dtsongUse when defining minimum viable scope for a product or feature launch. Covers MoSCoW prioritization, value-effort matrix analysis, MVP cut-line definition, and phased roadmap planning. Do not use for quantified feature comparison (use impact-estimation) or measurement instrumentation (use analytics-design).
- ▌ Git Conflicts 2 · dtsongUse when resolving merge or rebase conflicts with step-by-step guided resolution.
- ▌ CSS Layout Debugger 2 · dtsong bundleUse when a user reports CSS, layout, or styling issues in a Next.js application — "element overlapping," "spacing is wrong," "responsive layout broken," "dark mode not working," "Tailwind classes not applying," or "alignment off." Diagnoses through a 6-phase pipeline that mirrors browser evaluation order, covering token resolution, cascade conflicts, layout models, stacking contexts, and viewport responsiveness. Handles Tailwind, CSS Modules, styled-components, and vanilla CSS. Not for JavaScript logic bugs, data fetching issues, or server-side rendering errors — route those to ui-bug-investigator.
- ▌ UI Bug Investigator 2 · dtsong bundleUse when a user reports a non-CSS UI bug in a Next.js App Router application — "blank page," "data not loading," "click does nothing," "hydration mismatch," "flicker on navigation," or "state not updating." Runs symptom-targeted diagnostic checks against a component map to identify rendering, state, event handling, and data flow issues. Not for CSS layout, styling, or visual design problems — route those to css-layout-debugger.
- ▌ Git Merge Main 2 · dtsongUse when merging the main branch into the current feature branch to pick up upstream changes.
- ▌ Journey Mapping 2 · dtsongUse when mapping complete user journeys through multi-step flows, onboarding sequences, or feature workflows. Covers entry points, happy paths, alternate paths, error states, friction analysis, and delight opportunities. Do not use for individual component interaction specs (use interaction-design).
- ▌ Prompt Engineering 2 · dtsongUse when designing, evaluating, or versioning system prompts for LLM-powered features. Covers instruction structure, chain-of-thought patterns, output format constraints, few-shot example selection, and prompt versioning strategy. Do not use for RAG pipeline design (use rag-architecture) or AI evaluation frameworks (use ai-evaluation).
- ▌ Page Component Mapper 2 · dtsong bundleUse when investigating any frontend issue before diagnosis or debugging — maps a Next.js route to its full component tree. Resolves "what components render on this page," "show me the component tree for /dashboard," or "trace imports for this route." Produces a ComponentMap artifact with server/client boundaries, props, hooks, data fetching, and styling metadata consumed by all downstream QA skills. Not for diagnosing bugs, fixing code, or generating tests — those are handled by specialist skills after mapping is complete.
- ▌ Codebase Context 2 · dtsongUse when analyzing an existing codebase for architecture, tech stack, conventions, and infrastructure. Covers project structure mapping, data model discovery, integration point cataloging, and constraint identification. Do not use for schema changes (use schema-design) or API contract definition (use api-design).
- ▌ Pattern Analysis 2 · dtsongUse when auditing codebase patterns or evaluating proposed changes for convention consistency. Covers file naming, component patterns, data fetching, state management, and type conventions. Do not use for test plan design or coverage targets (use testing-strategy).
- ▌ Competitive Analysis 2 · dtsongUse when designing features that exist in competing products or analyzing prior art in the market. Covers feature mapping, UX evaluation, technical trade-off assessment, and differentiation opportunity identification. Do not use for evaluating individual libraries (use library-evaluation) or assessing technology maturity (use technology-radar).
- ▌ Git Delete Branch 2 · dtsongUse when deleting local or remote branches with safety checks for unmerged work.
- ▌ Interaction Design 2 · dtsongUse when designing component interaction specs with visual states, transitions, and accessibility requirements. Covers state matrices, responsive behavior, ARIA compliance, and content constraints. Do not use for multi-step user journey mapping (use journey-mapping).
- ▌ Data Classification 2 · dtsongUse when classifying data elements by sensitivity tier and defining per-tier handling requirements. Covers data inventory, sensitivity classification, PII flow mapping, encryption and masking specifications, and cross-boundary transfer documentation. Do not use for regulatory gap analysis (use compliance-review) or audit logging design (use audit-trail-design).
- ▌ Impact Estimation 2 · dtsongUse when comparing multiple features or initiatives to determine prioritization order. Covers RICE scoring with quantified reach, impact, confidence, and effort dimensions, tier ranking, and success metric definition. Do not use for MVP scope definition (use mvp-scoping) or analytics instrumentation planning (use analytics-design).
- ▌ Documentation Plan 2 · dtsongUse when designing documentation architecture for a project or team. Covers audience mapping, Diataxis framework classification, onboarding path design, format and location decisions, documentation testing, and maintenance scheduling. Do not use for recording individual architecture decisions (use adr-template) or creating versioned changelogs (use changelog-design).
- ▌ Failure Mode Analysis 2 · dtsongUse when systematically identifying failure scenarios for proposed features and infrastructure changes. Covers component enumeration, failure mode discovery, cascade analysis, mitigation design, monitoring signals, and rollback planning. Do not use for security threat modeling (use threat-model) or input boundary testing (use edge-case-enumeration).
- ▌ Formal Spec 2 · dtsongUse when writing formal specifications in TLA+ to verify system properties, defining state variables, configuring TLC model checker, and documenting assumptions and limitations. Covers safety and liveness properties for protocols and concurrent systems. Do not use for security claim enumeration without specification intent (use invariant-analysis).
- ▌ Crypto Review 2 · dtsongUse when reviewing cryptographic implementations for algorithm choice correctness, key management soundness, side-channel resistance, and crypto agility readiness. Covers symmetric and asymmetric operations, key lifecycle, and construction safety. Do not use for protocol-level analysis (use protocol-analysis) or post-quantum migration planning (use pqc-readiness).
- ▌ Pqc Readiness 2 · dtsongUse when assessing a system's readiness for post-quantum cryptography migration, inventorying classical crypto usage, mapping NIST-standardized PQC replacements, and planning phased migration timelines. Covers key exchange, digital signatures, and hybrid mode needs. Do not use for classical crypto implementation review (use crypto-review) or protocol state machine analysis (use protocol-analysis).
- ▌ Hw Sw Boundary 2 · dtsongUse when reviewing the hardware/software security interface to verify hardware security feature enablement, IOMMU/SMMU DMA protection configuration, and HW/SW trust model coherence. Covers boot chain verification, memory protection, and control flow integrity features. Do not use for kernel configuration audit (use kernel-hardening) or isolation boundary analysis (use isolation-review).
- ▌ Isolation Review 2 · dtsongUse when mapping isolation boundaries, enumerating crossing points, verifying enforcement mechanisms, and testing for bypass paths across trust domains. Covers containers, VMs, enclaves, namespaces, seccomp, and network segmentation. Do not use for kernel configuration audit (use kernel-hardening) or HW/SW security interface review (use hw-sw-boundary).
- ▌ Kernel Hardening 2 · dtsongUse when auditing kernel security configuration for memory protection, syscall surface reduction, control flow integrity, and integrity mechanisms against local and remote attack vectors. Covers CIS/KSPP benchmarks, KASLR, SMAP/SMEP, seccomp, and secure boot chain. Do not use for isolation boundary analysis (use isolation-review) or HW/SW interface review (use hw-sw-boundary).
- ▌ Protocol Analysis 2 · dtsongUse when analyzing cryptographic protocol security by modeling state machines, enumerating transitions, and identifying desynchronization, replay, downgrade, and session binding vulnerabilities. Covers protocol handshakes, session management, and negotiation integrity. Do not use for implementation-level crypto review (use crypto-review) or post-quantum assessment (use pqc-readiness).
- ▌ Invariant Analysis 2 · dtsongUse when enumerating security claims from a design, formalizing them as invariants, checking for hidden assumptions, and assessing verification feasibility. Covers safety invariants, temporal properties, and verification tool recommendations. Do not use for writing TLA+ specifications directly (use formal-spec) or implementation-level security review.
- ▌ Suite Name 2 · dtsong bundleTRIGGER_DESCRIPTION. Use when USER_CONTEXT. Routes to specialists for CAPABILITIES.
- ▌
- ▌
- ▌ Workflow 2 · dtsongUse when planning implementation steps, deciding commit format, or structuring development approach. Provides brainstorm-plan-implement flow with conventional commits. Triggers on 'how should I approach this', 'commit format'.
- ▌ Cicd Generation 2 · dtsong bundleUse when creating GitHub Actions workflows, adding CI/CD to a project, or reviewing pipeline security. Produces fail-fast, security-hardened workflows with OIDC auth and SHA-pinned actions. Triggers on 'add CI', 'create workflow', 'github actions'.
- ▌ Helm Generation 2 · dtsongUse when creating Helm values.yaml files, converting docker-compose to Helm, or reviewing Helm configurations. Produces minimal-diff values that only override chart defaults. Triggers on 'helm values', 'create values.yaml', 'deploy to kubernetes'.
- ▌ Dockerfile Generation 2 · dtsong bundleUse when creating Dockerfiles, optimizing container images, or reviewing Docker configurations. Produces multi-stage, security-hardened builds with proper layer caching. Triggers on 'create Dockerfile', 'dockerize', 'optimize container'.
- ▌ A11Y Audit 2 · dtsongUse when auditing accessibility compliance of a feature or codebase. Covers WCAG 2.2 AA conformance, screen reader compatibility, keyboard navigation, focus management, color contrast, reduced motion, and ARIA usage. Do not use for general UX review (use journey-mapping) or component interaction specs (use interaction-design).
- ▌ Load Modeling 2 · dtsongUse when planning capacity or projecting infrastructure needs under growth. Covers traffic modeling, endpoint heat maps, scaling triggers, benchmark design, and cost-at-scale estimates. Do not use for runtime bottleneck profiling (use performance-audit) or cache architecture design (use caching-strategy).
- ▌ Vercel React Best Practices 2 · dtsong bundleReact and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
- ▌ I18N Review 2 · dtsongUse when reviewing internationalization readiness of a feature or codebase. Covers locale strategy, RTL layout, string externalization, pluralization, date/number formatting, and cultural UX adaptation. Do not use for general accessibility audits (use interaction-design).
- ▌ API Design 2 · dtsongUse when designing REST or RPC endpoint contracts with request/response types and error handling. Covers endpoint specification, TypeScript type definitions, authentication requirements, pagination, and caching strategies. Do not use for database schema changes (use schema-design) or codebase analysis (use codebase-context).
- ▌ Visual Audit 2 · dtsongUse when performing structured visual design critique of an interface. Covers hierarchy, contrast, spacing, typography, color, and component consistency with actionable fix recommendations. Do not use for design token architecture (use design-system-architecture) or animation specifications (use motion-design).
- ▌ Ml Workflow 2 · dtsongUse when designing end-to-end ML workflows. Covers experiment tracking, feature engineering and storage, model training pipelines, serving and deployment, A/B testing, and drift monitoring. Do not use for data warehouse schema design (use schema-evaluation) or ETL pipeline architecture (use pipeline-design).
- ▌ Motion Design 2 · dtsongUse when designing the motion language for a feature or system. Covers transition specs, micro-interaction definitions, choreography principles, performance constraints, and reduced-motion alternatives. Do not use for visual design critique (use visual-audit) or design token architecture (use design-system-architecture).
- ▌ E2e Testing 2 · dtsongUse when designing end-to-end test suites, visual regression testing, or cross-browser test strategies. Covers Playwright/Cypress test architecture, page object patterns, test data management, visual snapshot comparison, cross-browser matrix, and CI integration. Do not use for unit/integration test strategy (use testing-strategy) or code pattern audit (use pattern-analysis).
- ▌ Caching Strategy 2 · dtsongUse when designing or auditing a caching architecture. Covers multi-layer cache hierarchy, key schema, TTL policies, invalidation flows, and warming strategies. Do not use for runtime performance profiling (use performance-audit) or capacity planning (use load-modeling).
- ▌ Schema Design 2 · dtsongUse when designing or modifying database schemas with migration plans. Covers entity definition, relationship mapping, normalization trade-offs, indexing strategies, and RLS policies. Do not use for API endpoint contracts (use api-design) or codebase analysis (use codebase-context).
- ▌ Adr Template 2 · dtsongUse when recording significant architectural or design decisions that affect the system. Covers decision framing, context documentation, options analysis with tradeoff evaluation, consequence mapping, and review trigger definition. Do not use for documentation strategy planning (use documentation-plan) or release changelog creation (use changelog-design).
- ▌ RAG Architecture 2 · dtsongUse when designing a Retrieval-Augmented Generation pipeline. Covers document processing, chunking strategy, embedding pipeline, vector database selection, retrieval optimization, and context assembly. Do not use for prompt design (use prompt-engineering) or evaluation framework design (use ai-evaluation).
- ▌ Performance Audit 2 · dtsongUse when profiling application performance or diagnosing slow page loads. Covers full-stack bottleneck identification including Core Web Vitals, bundle analysis, database queries, and network waterfall. Do not use for cache architecture design (use caching-strategy) or capacity planning (use load-modeling).
- ▌ Microarch Analysis 2 · dtsongUse when analyzing microarchitectural attack surfaces by mapping shared hardware structures, identifying speculative execution vectors, quantifying speculative windows, and proposing countermeasures. Covers cache timing, transient execution, and contention channels. Do not use for RTL-level design review (use rtl-security-review) or physical implementation analysis (use physical-design-security).
- ▌ Deployment Plan 2 · dtsongUse when designing deployment strategies including environment progression, CI/CD pipelines, zero-downtime releases, rollback procedures, and feature flag management. Covers blue-green, rolling, and canary deployment patterns with database migration coordination. Do not use for monitoring or alerting design (use observability-design) or infrastructure cost modeling (use cost-analysis).
- ▌ Finops Analysis 2 · dtsongUse when analyzing cloud spending, cost attribution, or unit economics. Covers cost allocation tagging, reserved capacity planning, right-sizing, spot/preemptible usage, cost anomaly detection, and showback/chargeback models. Do not use for general infrastructure cost modeling (use cost-analysis) or deployment strategy (use deployment-plan).
- ▌ Library Evaluation 2 · dtsongUse when adding new packages, choosing between dependency alternatives, or auditing existing libraries. Covers popularity metrics, maintenance health, bundle impact, API quality, and license compatibility with weighted scoring. Do not use for evaluating frameworks or platforms (use technology-radar) or comparing competing products (use competitive-analysis).
- ▌ Protocol Design 2 · dtsongUse when selecting and designing communication protocol stacks for IoT or embedded systems. Covers physical layer selection, transport and application protocols, security layers, message format design, and error resilience. Do not use for firmware architecture (use embedded-architecture) or fleet-scale operations (use fleet-management).
- ▌ Pipeline Design 2 · dtsongUse when designing data pipelines for moving, transforming, and delivering data. Covers ETL vs ELT pattern selection, orchestration tool choice, batch vs streaming trade-offs, idempotency guarantees, data quality checkpoints, and lineage tracking. Do not use for schema modeling (use schema-evaluation) or ML workflows (use ml-workflow).
- ▌ Rtl Security Review 2 · dtsongUse when reviewing RTL designs for security vulnerabilities including access control gate bypasses, insecure FSM transitions, timing-dependent information leakage, and unintended data paths. Covers Verilog, SystemVerilog, and VHDL modules with security-critical functions. Do not use for physical implementation review (use physical-design-security) or microarchitectural attack analysis (use microarch-analysis).
- ▌ Growth Engineering 2 · dtsongUse when designing growth infrastructure including onboarding funnels, referral mechanics, A/B test instrumentation, and re-engagement loops. Covers activation metrics, funnel mapping, and experimentation design. Do not use for pricing or paywall architecture (use monetization-design) or product copy and naming (use messaging-strategy).
- ▌ Messaging Strategy 2 · dtsongUse when developing product messaging frameworks including value propositions, feature naming, microcopy guidelines, and CTA strategy. Covers voice and tone definition, conversion copy, and upgrade prompt language. Do not use for pricing architecture or paywall placement (use monetization-design) or onboarding funnels and referral systems (use growth-engineering).
- ▌ Platform Audit 2 · dtsongUse when auditing a feature or implementation against platform-specific guidelines such as iOS HIG, Material Design 3, and WCAG. Covers compliance scoring, violation identification, remediation steps, and App Store risk assessment. Do not use for navigation architecture (use navigation-design) or hardware API integration (use device-integration).
- ▌ Fleet Management 2 · dtsongUse when designing fleet management infrastructure for IoT device fleets. Covers device provisioning, OTA firmware update strategy, telemetry pipeline design, fleet monitoring, remote management, and scaling projections. Do not use for firmware architecture (use embedded-architecture) or wireless protocol selection (use protocol-design).