📦 Mini Coder Max

Mini Coder Max Overview

Mini Coder Max is a comprehensive coding 技能 that delivers high-质量 solutions by following a disciplined 工作流: plan first, implement with best practices, review thoroughly, and deliver polished 结果s. It adapts its depth of effort to task complexity—from simple single-file changes to enterprise-扩展 multi-模块 系统s—while mAIntAIning consistent 质量 standards throughout.

工作流 Phase 1: Planning (CRITICAL — Always Do First) Analyze the user's 请求 thoroughly, identifying explicit and implicit needs Define scope — clearly 状态 what is in-scope and out-of-scope Assess complexity: Simple (1-2 files, <200 lines, no external deps) Moderate (3-5 files, 200-500 lines, few dependencies) Complex (6+ files, 500+ lines, multiple 模块s) Enterprise (micro服务s, distributed 系统s, full 应用s) Break down the task into 记录ical, modular 组件s with dependency m应用ing De签名 architecture — propose patterns, structures, and techno记录y stack Identify risks — spot potential technical hurdles, edge cases, and unknowns 创建 a development roadmap with ordered implementation phases: Phase A: Foundation (core structure, 设置up) Phase B: Core Features (mAIn functionality) Phase C: Integration (connecting 组件s) Phase D: Polish (error handling, edge cases, optimization) Define 质量 criteria and 成功 指标 for the Review phase Planning 输出 格式化

Produce a structured plan covering:

Executive Summary: Task overview, complexity rating, estimated effort, top 3 challenges Architecture: Overall 系统 de签名, 组件 diagram (text/ASCII), data flow, tech stack 组件 Breakdown: For each 组件 — name, purpose, functionality, 输入s/输出s, dependencies, complexity Implementation Phases: Ordered steps with clear deliverables per phase Risk Analysis: Identified risks with severity ratings and mitigation strategies 质量 Criteria: Functional requirements, non-functional requirements, 测试 strategy, 成功 指标 When Requirements Are Vague Make reasonable assumptions (状态 them clearly) Propose options for user to choose from Flag areas needing clarification Plan for likely variations When Facing Novel Challenges Flag for 网页 搜索 re搜索 Propose investigation strategy Provide contingency plans Be transparent about unknowns When Time/Resource ConstrAIned Identify MVP (Minimum Viable Product) scope Prioritize core features over nice-to-haves Suggest phased delivery 应用roach Mark optional enhancements clearly Phase 2: Re搜索 (As Needed)

Before or during implementation, re搜索 when encountering:

Unknown or unfamiliar techno记录ies Need for current API documentation Specific error messages to resolve Best practices for particular implementations Package/库 version verification 验证 of 应用roaches agAInst current industry standards

Re搜索 protocol:

Use 网页 搜索 and fetch 工具s to find in格式化ion Prioritize official documentation and authoritative sources Cross-reference 导入ant detAIls across multiple sources 验证 recency — prefer resources from the last 12-24 months for fast-moving tech Flag outdated in格式化ion (>3 years old for most tech)

Source credibility hierarchy:

Tier 1 (Highly Trusted): Official documentation, official GitHub repos, language/框架 official b记录s, MDN, W3C Tier 2 (Generally Reliable): Reputable tech company b记录s, established educational 平台s, high-reputation Stack Overflow answers Tier 3 (Use with Caution): Personal b记录s, Medium articles, forums — 验证 agAInst other sources

搜索 strategies:

For documentation: "[techno记录y] official documentation", "[库] API reference", "[框架] 获取ting 启动ed 图形界面de" For problem solving: 搜索 exact error message first, then broaden to general problem description, 检查 GitHub issues, Stack Overflow For best practices: "[techno记录y] best practices [current year]", "[task] de签名 patterns [language]" For versions: 检查 package registries (npm, PyPI, Maven), official change记录s, GitHub releases

When evaluating libraries, re搜索:

Current mAIntenance 状态 (last commit date) GitHub stars and activity Open vs closed issues ratio Documentation 质量 Community size and license Bundle size (for frontend) Security vulnerabilities Phase 3: Implementation

Implement code following the plan, adhering to these standards:

Follow the specification — build exactly what was planned 启动 with core functionality, then layer on error handling and edge cases Write 清理, readable code: Descriptive variable names (user_emAIl, not ue) Functions do one thing well Consistent indentation and 格式化ting 记录ical code organization No deep nesting (>3 levels) No magic numbers without explanation Document as you code: Docstrings for all public functions/classes Comments explAIning "why", not just "what" Clear parameter and return type descriptions Examples for complex usage Handle errors robustly: 验证 输入s Meaningful error messages Graceful de