mindscape-dev-guide

Enforce Mindscape AI local-core development rules for architecture, code style, Git workflow, and documentation.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/HansC-anafter/mindscape-ai-local-core --skill mindscape-dev-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mindscape-dev-guide
Source: https://github.com/HansC-anafter/mindscape-ai-local-core/tree/main/.agent/skills/mindscape-dev-guide
Command: npx skills add https://github.com/HansC-anafter/mindscape-ai-local-core --skill mindscape-dev-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures adherence to critical development standards within the Mindscape AI local-core project, preventing architectural violations, code style inconsistencies, and workflow errors.

Core Features & Use Cases

  • Architecture Enforcement: Prevents forbidden cross-repo file system access and ensures local-core remains a pure runtime.
  • Code Quality: Enforces strict English-only language rules for code, comments, and logs, along with specific Python and TypeScript style guides.
  • Workflow Compliance: Mandates Conventional Commits, a clear branch strategy, and a PR checklist to maintain code integrity and traceability.
  • Use Case: A developer attempting to commit code that includes Chinese comments or tries to read from an external repository will be flagged by this Skill, ensuring compliance before the commit is finalized.

Quick Start

Ensure all code comments and logger messages are in English only.

Frequently Asked Questions about mindscape-dev-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce architecture boundaries and prevent cross-repo file system access in my local-core project?

To enforce architecture boundaries and prevent cross-repo file system access, this development guide validates your codebase to ensure local-core remains a pure runtime, flagging any forbidden file system access before commit finalization.

What code style rules are enforced for Python and TypeScript development?

The enforced code style rules mandate PEP 8 for Python and TypeScript interface standards, requiring strict English-only language for all code comments, docstrings, and logger messages.

How do I enforce Conventional Commits and a branch strategy for code integrity?

To enforce Conventional Commits and a defined branch strategy, this guide mandates specific commit message formats and applies a PR checklist to maintain code integrity and traceability.

Can I use platform-specific business APIs within the local-core runtime?

No, you cannot use platform-specific business APIs within the local-core runtime. This guide validates against their inclusion to ensure the local-core remains a pure, platform-agnostic runtime.

Why does my commit get flagged when including raw capability source in core?

Your commit gets flagged because this guide prevents raw capability source inclusion in core to maintain architectural purity. It validates against this practice to ensure compliance before finalizing.

What documentation conventions do I need to follow for Mindscape development?

For Mindscape development, you need to follow documentation conventions that require English-only docstrings and comments, aligning with PEP 8 and TypeScript interface standards to ensure consistency.