Mobile Engineering Agents

Appearance

Workflow: Verify Toolkit Setup ​

Confirms the toolkit is intact after installing, cloning, or pulling. Ensures all entry points, core directories, and expected file counts are present and ready for use.

Objective ​

Confirm that the toolkit has been properly initialized and all critical files and directories exist.

Inputs ​

  • The current working directory (repo root).

Outputs ​

  • A pass/fail report with ✓/✗ per check.
  • A final health summary: either "Toolkit is healthy — ready to use" or a list of missing/short items with recovery suggestions.

Step-by-Step Process ​

  1. Check for an npx install first — if .mobile-agents/.mobie-manifest.json exists, the toolkit was installed with npx @sok_pich/mobie and holds only the installed platform's skills and templates. Run npx @sok_pich/mobie doctor from the project root, report its output, and stop here. The count thresholds below apply only to a full clone.

  2. Check entry point files exist — verify these files are present at the repo root:

    • CLAUDE.md
    • GEMINI.md
    • .cursorrules
    • .windsurfrules
    • AGENTS.md

  3. Check core directories exist — verify these directories are present:

    • agents/
    • skills/
    • workflows/
    • checklists/
    • standards/
    • templates/
    • architecture/

  4. Check expected file counts — ensure minimum thresholds are met. These mirror verify.sh; update both together:

    • agents/*.md ≥ 17
    • skills/**/*.md ≥ 53
    • workflows/*.md ≥ 13
    • checklists/*.md ≥ 10
    • standards/*.md ≥ 10

    Then check per-platform coverage:

    • skills/*/ios/**.md ≥ 34, and templates/ios/ exists
    • skills/*/flutter/**.md ≥ 17, and templates/flutter/ exists

  5. Report each check — display ✓ for pass, ✗ for fail.

  6. Print health summary — on all pass, print:

    Toolkit is healthy — ready to use

    On any fail, list missing/short items and suggest:

    • Run git status to check for missing files

    • Re-clone if the issue persists:

      bash
      git clone https://github.com/sokpichdev/mobie.git

Validation Steps ​

  • Entry point files are readable at the repo root.
  • All core directories exist and are accessible.
  • File counts meet the specified minimums.

Failure Scenarios ​

  • Missing entry point files → Check recent git pull or clone; some files may not have been fetched.
  • Missing directories → Incomplete clone or repository structure issue; re-clone or restore from git.
  • File count shortfall → Files may have been deleted or moved; restore from git checkout or re-clone.

AI Agent Instructions ​

  • Verify by reading directory listings and file counts — no shell commands required.
  • Be thorough: check all entry points and all core directories before declaring pass.
  • If any single check fails, the overall health is fail; list all failures and suggest recovery steps.
  • Do not proceed with task guidance if the toolkit is not healthy.

Acceptance Criteria ​

  • [ ] All five entry point files confirmed present.
  • [ ] All seven core directories confirmed present.
  • [ ] All file count thresholds met.
  • [ ] Health summary printed (pass or fail with guidance).