Affaan Mustafa

Record software design decisions as numbered Markdown files, with context, rejected alternatives, benefits, drawbacks, and risks. Maintain an index and consult existing ADRs—architecture decision records—to explain why a framework, database, or design approach was chosen.

• Record reasons for framework or database choices
• Document design alternatives and trade-offs
• Find explanations for past technical decisions

Choose which competitors to compare based on a company's offer, audience, and positioning. Organize candidates into direct, adjacent, and aspirational groups, then narrow the list with selection scores and source links before detailed benchmarking.

• Defining the competitor set before a benchmarking project
• Grouping direct, adjacent, and aspirational competitors
• Narrowing candidates for a market landscape report

Add an external API integration that follows the project's existing structure. Use current connectors as models for configuration, authentication, error handling, registration, and tests, so the new integration fits the surrounding code.

• Adding a Jira connector to an existing project
• Building a Slack provider using current project conventions
• Completing integration registration and tests

Turn a large engineering objective into a written plan with steps sized for individual pull requests, or proposed code changes. Each step includes context, dependencies, checks, and completion criteria so another agent can continue the work.

• Splitting a large feature into multiple pull requests
• Planning a migration across several sessions
• Identifying steps agents can work on in parallel

Turn scored competitor profiles into a report for strategic decisions. Organize market maps, comparison tables, unoccupied positions, threats, and prioritized recommendations so leaders can decide whom to compete with and how to differentiate.

• Preparing a competitive report for leadership or a board
• Combining completed competitor profiles
• Assessing room for differentiation and competitive threats

Create CodeTour files that guide readers through a codebase step by step, with verified file and line references. Tailor the walkthrough to new contributors, architecture readers, PR reviewers, or investigators tracing a failure or security boundary.

• Creating onboarding walkthroughs for new maintainers
• Explaining architecture and feature execution paths
• Guiding reviewers through PR changes

Structure Android and Kotlin Multiplatform projects with clear boundaries between business logic, screens, and data access. Provides examples for module dependencies, business operations, repositories that coordinate data sources, database integration, and error handling.

• Planning Android or KMP module boundaries
• Separating business logic from screen code
• Coordinating local and remote data sources

Review how easy code is to maintain using CodeScene MCP. Compare structural health scores before and after edits, identify design issues, and check commits and pull requests for changes that reduce maintainability.

• Reviewing an unfamiliar file before editing
• Checking whether AI edits reduce maintainability
• Refactoring while comparing health scores

Turn articles, notes, demos, and transcripts into posts, video scripts, and newsletters for X, LinkedIn, TikTok, and YouTube. Adapt each draft to its platform while preserving the author's voice and grounding it in specific source material.

• Adapt one article into posts for several platforms
• Draft a sequence of product launch posts
• Create short video and YouTube scripts

Build a reusable writing style profile from real posts, articles, emails, and product copy. Use it to keep social posts, outreach, and launch announcements consistent in tone, sentence rhythm, and expression across related writing tasks.

• Keep a consistent voice across social channels
• Match outreach emails to an established writing style
• Reuse an author's tone in product announcements

Draft articles, guides, and newsletters in a voice drawn from supplied examples or brand guidance. Turn notes and research into structured prose, or revise existing drafts for clearer pacing, stronger evidence, and consistent style.

• Turning notes and transcripts into articles
• Drafting guides in a consistent brand voice
• Revising the structure and evidence of existing drafts

Develop a written brand identity through structured interviews across multiple sessions. Save answers and progress, explore founders' perspectives, and produce a master brandbook that gives designers, writers, and collaborators a shared reference.

• Defining the identity of a new brand
• Revisiting a brand's market positioning
• Preparing a brief for designers and writers

Design a persistent multi-agent workflow in Claude Code, with specialist roles, reusable commands, file-based memory, and scheduled tasks. Keep project context and decisions across sessions using JSON and Markdown files without an external database.

• Coordinate specialist agents for development and writing
• Preserve project context across sessions
• Schedule recurring morning briefings