Thanks for your interest in contributing to Mobile App Developer Tools.
- Fork the repository
- Create a feature branch (
git checkout -b feature/my-feature) - Make your changes
- Run the test suite (
pip install -r requirements-test.txt && pytest tests/ -v) - Build the MCP server (
cd mcp-server && npm install && npm run build) - Commit your changes and open a pull request
- Create a directory under
skills/matching your skill name (e.g.skills/mobile-my-skill/) - Add a
SKILL.mdfile with YAML frontmatter containingname(must match directory) anddescription - Include these required sections in order: Trigger, Required Inputs, Workflow, Example Interaction, MCP Usage, Common Pitfalls. Optional sections: Key References, See Also
- Run
pytest tests/test_skills.py -vto verify frontmatter and structure
- Create a
.mdcfile underrules/(e.g.rules/mobile-my-rule.mdc) - Include YAML frontmatter with
descriptionandalwaysApply(boolean) - If
alwaysApplyis false, addglobsto scope when the rule activates - Run
pytest tests/test_rules.py -vto verify frontmatter
- Create a tool file under
mcp-server/src/tools/(e.g.myTool.ts) - Export a
register(server: McpServer): voidfunction - Use the
mobile_camelCasenaming convention (e.g.mobile_myTool) - Import and register the tool in
mcp-server/src/index.ts - Build and test:
cd mcp-server && npm run build
See .cursorrules for writing conventions. Key points:
- No em dashes
- No filler words
- Active voice
- Code over prose
- Parallel structure in lists
Open an issue on GitHub. Include steps to reproduce, expected behavior, and actual behavior.