dividox

Deep audit of authentication and session management against OWASP MASVS-AUTH controls. Use when code touches login, logout, token storage, token refresh, biometrics, or Google Sign-In.

Generate a full OWASP MASVS v2 compliance checklist for Dividox with MASTG test mappings. Use before a release, for a compliance review, or when assessing overall security posture.

Deep audit of code quality and supply chain security against OWASP MASVS-CODE controls. Use when modifying libs.versions.toml dependencies, minSdk, R8/ProGuard rules, or input validation logic. This is the primary skill for Detekt-detectable issues.

Deep audit of cryptographic implementations against OWASP MASVS-CRYPTO controls. Use when code generates keys, encrypts/decrypts data, uses hashing, or touches AndroidKeyStore / iOS Keychain.

Generate a STRIDE threat model for Dividox mapped to MASVS controls with NowSecure risk tiering. Use when designing new features with a significant security surface, or for periodic threat reviews.

Deep audit of network communication security against OWASP MASVS-NETWORK controls. Use when code configures HTTP clients (Ktor, OkHttp), touches TLS, certificates, or network_security_config.xml.

Deep audit of platform interaction security against OWASP MASVS-PLATFORM controls. Use when code touches deep links, Intents, exported components, WebViews, or AndroidManifest/Info.plist.

Deep audit of privacy controls against OWASP MASVS-PRIVACY controls. Use when code touches permissions, analytics SDKs, user identifiers, consent flows, or data export/deletion.

Audit of anti-tampering and reverse engineering resilience against OWASP MASVS-RESILIENCE controls. Tier 3 only — optional for Dividox unless regulatory or contractual requirements apply. Use when implementing root/jailbreak detection, obfuscation, or anti-debug measures.

Deep audit of data-at-rest security against OWASP MASVS-STORAGE controls. Use when code writes sensitive data to disk: SharedPreferences, DataStore, Room/SQLite, files, logs, clipboard, or backups.

Scaffolds the UI Layer (Presentation) including MVI Contract, ViewModel, Composable Screen, Navigation, and DI wiring. Use when creating new screens, adding UI features, or implementing presentation logic with MVI pattern.

Guide for writing unit tests for ViewModels, UseCases, and Extensions. Use this skill when you need to create a new unit test, following the project's standard patterns like GIVEN/WHEN/THEN naming.

Describes and enforces the type-safe KMP navigation pattern. Use when adding new screens, routes, or navigation flows to the app.

Audit and improve Jetpack Compose runtime performance from code review and architecture. Use when asked to diagnose slow rendering, janky scrolling, excessive recompositions, or performance issues in Compose UI.

Generates C4 model diagrams (Context, Container, Component levels) using Mermaid for a specific system or subsystem. Use when you need to document the architecture at multiple zoom levels following the C4 model. Part of the Solutioning phase of product documentation.

Generates a data model with Entity-Relationship Diagram (ERD) using Mermaid, entity descriptions, and relationship documentation. Use when designing the persistence layer or domain model of a product. Part of the Solutioning phase of product documentation.

Generates a high-level system design including architecture overview, service decomposition, technology stack, and system architecture diagram. Use when designing the technical architecture of a product. Part of the Solutioning phase of product documentation.

Estimate development effort for user stories and sprint backlogs using Planning Poker (Fibonacci) broken down by technology layer, combined with MoSCoW prioritization. Use when asked to estimate stories, size a sprint, produce a capacity plan, or run a planning session. Triggers on: "estimate this story", "how many points", "size the backlog", "sprint capacity", "planning poker", "effort for US-NNN", "capacity planning", "estimate the sprint", "story points", "t-shirt size", "planning session".

Orchestrates the full product documentation lifecycle by invoking all documentation skills in sequence across four phases - Description, Planning, Solutioning, and Roadmap. Use when you need to generate complete product documentation from scratch or when starting a new product design project.

Generates Architecture Decision Records (ADRs) documenting key technical decisions with context, alternatives, and consequences. Use when documenting architectural choices such as technology selection, patterns, infrastructure, or design trade-offs. Part of the Solutioning phase of product documentation.

Generates Product Requirements Documents (PRDs) for specific features or use cases. Use when planning features that need detailed requirements, user stories, acceptance criteria, and release plans. Part of the Planning phase of product documentation.

Expert on Dependency Injection (DI) configuration using Koin for Kotlin Multiplatform projects. Use this skill when configuring modules, registering dependencies, or setting up test overrides.

Scaffolds the Logic Layer (Domain & Data) including Use Cases, Repositories, Data Sources, Domain Models, and DI wiring. Use when implementing business logic, data access, domain rules, or creating new components following Clean Architecture.

Git workflow management for projects. Use when developers need to (1) create properly formatted Git branches following feature/{ticket}-{description} pattern, (2) format commit messages with ticket prefixes, (3) generate Pull Request titles and descriptions, (4) validate branch names or commit messages against project standards, or (5) get step-by-step workflow guidance for feature development or bug fixes.

Defines the multi-module KMP architecture for Dividox (app/feature/integration/component/common). Use when creating new modules, deciding where code belongs, or onboarding to the project structure.

Reviews code against OWASP MASVS (Mobile Application Security Verification Standard) controls. Use when code handles sensitive data, authentication, networking, local storage, or deep links. Reports findings as PASS / WARN / FAIL.

Generates the Description phase of a product design document including brainstorming, market analysis, product brief, main functions, lean canvas, and main use cases. Use when starting a new product design from scratch or when you need to document the discovery/description phase of a software product.

Generates a product roadmap with phased delivery plan, Gantt chart, milestones, and detailed phase breakdowns. Use when planning the timeline and delivery sequence of a product. Part of the Roadmap phase of product documentation.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Unified entry point for Stitch design work. Handles prompt enhancement (UI/UX keywords, atmosphere), design system synthesis (.stitch/DESIGN.md), and high-fidelity screen generation/editing via Stitch MCP.

Generate a User Story Map organizing user stories visually by activity flow and priority, with release cut lines. Use when asked to create a story map, organize existing user stories, plan releases or MVP scope, or visualize the full user journey. Triggers on phrases like "story map", "user story map", "map the user journey", "plan the MVP", "organize backlog", "what goes in the MVP".

Plan tasks for implementation, creating subtasks in a task-specific `task.md` file. Use when breaking down features into actionable implementation steps.

Generate Agile work tickets (Features, Technical Tasks, Bugs, Improvements, Spikes) from user stories. Use when asked to create tickets, break down a user story into tasks, generate sprint tickets, create work items, decompose a story into technical tasks, or populate a sprint backlog. Triggers on phrases like "generate tickets", "create tasks from this story", "break down into tickets", "sprint tickets for US-NNN", "decompose this story", "create work items", "technical tasks for this story", "what tickets do we need".

Write well-formed user stories following INVEST criteria and BDD acceptance criteria. Use when asked to write user stories, create backlog items, break down an epic into stories, or refine existing stories. Triggers on phrases like "write user story", "create user stories", "backlog item", "break down this epic", "refine this story", "evaluate INVEST".

Expert in transforming vague ideas into professional, structured prompts optimized for Kotlin Multiplatform Engineering. Use this skill when you need to create clear, actionable prompts for AI agents or team members.