TechLeads.club 💎

Build iOS and Android apps with React Native and Expo. Get guidance and typed component code for navigation, lists, animations, storage, and platform differences, with attention to scrolling performance and testing on both platforms.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building mobile screens with React Native and Expo
• Adding screen navigation with Expo Router
• Improving list scrolling and animation performance

Apply a specific set of Rails conventions to design, implementation, and code review. It keeps business logic in models, represents state changes as records, limits dependencies, and uses Minitest with fixtures, or predefined test data.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing Rails models and database changes
• Representing state changes with separate records
• Reviewing code for consistent Rails conventions

Build and troubleshoot Shopify themes, apps, and custom storefronts with task-specific references. It covers Liquid, Shopify’s template language, API data access, custom business rules, and performance improvements, using API version 2026-01.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Write and debug Liquid templates
• Customize OS 2.0 themes
• Build Shopify apps and API integrations

Explore an early software idea through an interview, clarify the problem, and decide whether to proceed. Produce a design document covering decisions, flows, data structures, and interface agreements so others can plan the work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarifying the problem behind a proposed feature
• Deciding whether to build, postpone, or reduce scope
• Exploring alternatives before committing to development

Analyze a monolithic codebase before splitting it into modules or services. The skill inventories components, examines duplication, hierarchy, and dependencies, then proposes groupings aligned with business domains, with optional checks against business terminology and boundaries.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assessing component sizes before splitting a monolith
• Finding duplicated business logic across modules
• Reviewing module hierarchy and dependencies

Review domain code for classes that hold data while business logic lives elsewhere. Using domain-driven design patterns, diagnose problems and refactor objects to keep business rules, state changes, and validation together, with before-and-after diffs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing domain models against DDD patterns
• Finding classes that only hold data
• Moving business rules into domain objects

Guide feature development from a human-reviewed plan to testable requirements, implementation, and independent verification. Record each requirement with a concrete proof, then have a separate agent check the work and produce a verification report.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare a feature plan for human review
• Turn approved requirements into checks with concrete proof
• Implement a feature against agreed checks

Turn an agreed specification or ticket into a checklist with specific tests or commands for each requirement. Implement the work, run the checks, and have a separate agent verify the entire feature.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implement a feature from an agreed specification
• Extract verifiable requirements from a ticket
• Verify every requirement with a separate agent

Create ADRs, short records of architectural decisions, that explain what was chosen, why, and with what trade-offs. Choose among three formats and organize dates, status, numbering, and related links for future team members.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recording why a database was chosen
• Preserving the rationale for a framework choice
• Documenting an authentication approach

Plan and implement features with a workflow that adapts to their complexity. It connects testable requirements to tasks, tests, and small commits, then checks the finished work against the specification through an independent verification pass.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Define testable requirements for a new feature
• Implement a large feature through small, verified tasks
• Check whether an implementation meets its specification

Guide an AI agent through research, implementation, and verification with fewer interruptions. The skill emphasizes evidence, concise reporting, and saved progress notes, with three working modes that adjust how closely the user follows the work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Delegating engineering tasks through verification
• Reducing interruptions during focused work
• Resuming long tasks from saved progress notes

Plan personalized sales emails to prospects you have not contacted before. This skill covers prospect selection, contact research, email drafts, follow-up sequences, inbox delivery, and reply handling, with guidance on tools and campaign improvements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Drafting personalized sales emails for new prospects
• Planning a sequence of emails and follow-ups
• Investigating low reply rates or spam placement

Fetch design structure, screenshots, variables, and assets from Figma through MCP, a connection between the agent and Figma. Use these references to guide code implementation within an existing project and troubleshoot connection setup.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Inspecting a specific Figma frame or layer
• Fetching images and SVG assets for implementation
• Adapting a design to existing project components

Evaluate code against a product requirements document, scoring implementation and tests separately for each acceptance criterion. Produce an evidence-backed final grade, identify gaps, and compare implementations using a fixed checklist and scoring method.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking whether a feature fulfills its requirements
• Comparing implementations of the same specification
• Auditing unit and end-to-end test coverage

Refactor React components that have too many true-or-false settings into reusable, flexible parts. This skill guides component composition, shared state, and API design, with examples and separate guidance for React 19 features.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Refactoring components with many boolean props
• Designing a reusable component library
• Organizing state shared by sibling components

Find business logic repeated across software components, such as notifications, auditing, and validation. Compare responsibilities and dependencies, then recommend a shared service, shared library, or component merger with a prioritized consolidation plan.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding duplicate business logic before refactoring
• Reviewing whether notification components should be merged
• Identifying candidates for shared services or libraries

Find classes left in parent folders or namespaces and identify nested component structures. Compare consolidation, splitting, and shared code extraction, then plan and carry out refactoring with updated references and tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find classes left in parent namespaces
• Compare consolidation and splitting of nested components
• Move shared utilities into a dedicated component

Map a codebase into architectural components, logical groups of source files, and compare their sizes using executable statements and file counts. Produce an inventory, identify unusually large or small components, and recommend where to split or consolidate code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a component inventory before splitting a monolith
• Find components with disproportionately large amounts of code
• Review small components for consolidation

Analyze dependencies between software modules using connection strength, distance, and frequency of change. Get a dependency map, code evidence, and prioritized recommendations for relationships that make changes spread across the system.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating why changes spread between modules
• Reviewing dependencies between services
• Prioritizing work to reduce coupling

Create a phased roadmap for splitting a monolithic application into separate services. Assess current progress, prioritize work by risk, value, and dependencies, and produce milestones, estimated effort, acceptance criteria, and progress reports.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning a migration from a monolith to separate services
• Prioritizing components for extraction
• Defining phase milestones and completion criteria

Analyze business concepts in a codebase to map business areas and suggest service boundaries. Use Domain-Driven Design, an approach organized around business meaning, to classify responsibilities, assess how closely they belong together, and recommend clearer integration points.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Mapping business capabilities in an unfamiliar codebase
• Planning service boundaries around business terminology
• Reviewing mixed responsibilities before refactoring

Organize existing code components into business areas to prepare for service separation. Produce domain maps, component assignment tables, and refactoring plans that align namespaces, the naming structure used to organize code, with business responsibilities.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Grouping existing components by business responsibility
• Planning service extraction from an existing application
• Aligning code namespaces with business areas