How do I install the Localsetup Framework Compliance skill?

Run npx skillmds@latest add majiayu000/localsetup-framework-compliance in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Localsetup Framework Compliance safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Localsetup Framework Compliance?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Localsetup Framework Compliance free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Localsetup Framework Compliance?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Localsetup Framework Compliance by majiayu000

Name: Localsetup Framework Compliance
Rating: 4.2 (5 reviews)
Author: majiayu000

Localsetup Framework Compliance

Pre-task workflow, certainty assessment, context load, document status, testing, Git checkpoints, document maintenance. Use for framework modifications, PRDs, or any task that must follow checklist and checkpoints.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

Framework compliance (pre-task, checkpoints, document maintenance)

0. MANDATORY PRE-TASK WORKFLOW (CRITICAL)

Before executing ANY task:

IDENTIFY TASK TYPE - file_creation, code_modification, framework_modification, git_operation, etc.
CHECK CORE RULES (BLOCKS EXECUTION IF VIOLATED): Engine/user data separation; Git checkpoints after framework modifications; Markdown compatibility; Testing after changes; Backup management.
ASSESS CERTAINTY - HIGH/MEDIUM/LOW/CRITICAL LOW; if <70% lookup docs; if <50% on core rules get user confirmation.
PRE-EXECUTION CHECKLIST - Use source lib/rule_enforcer_enhanced.sh && pre_execution_checklist "$task_type" "$task_description" (when available).
EXECUTE TASK with rule compliance monitoring.
POST-EXECUTION VERIFICATION - Use post_execution_verification "$task_type" "$task_context"; verify checkpoints and backups.

Documentation lookup: Check _localsetup/docs/, your platform's rules path (e.g. .cursor/rules/ on Cursor), _localsetup/config/rules_index.yaml. Never proceed with CRITICAL LOW certainty on core rules without user confirmation.

1. Context load and repo role

VERIFY: Context is loaded. If unsure, ask user to run ./_localsetup/tools/verify_context.
Repo role: Framework lives in client repo at _localsetup/. Only modify local context (e.g. your platform's local rules, such as .cursor/rules/local-*.mdc on Cursor) or propose changes via PRD. See REPO_AND_DATA_SEPARATION.md.

6. Document status and testing

Document status: Before referencing any document, check status (ACTIVE/PROPOSAL/DRAFT/DEPRECATED/ARCHIVED). If PROPOSAL, do not assume implemented. Use check_document_status() or _localsetup/docs/DOCUMENT_INDEX.yaml.
Testing: Run _localsetup/tests/automated_test.sh after changes; maintain 100% test pass rate.

14. Git checkpoints (CRITICAL)

MANDATORY: Create Git checkpoints IMMEDIATELY after framework modifications. Use _localsetup/tools/verify_rules to verify.
Checkpoint creation: Stage and commit with messages like "Checkpoint: - ". Never commit user/repo-local data that should stay private.
Rollback: git reset --hard <commit-hash> (with confirmation). List: git log --oneline.

16. Document maintenance after major task

Trigger: After major task completion, user validation, and Git commit.
Workflow: Document scrub first (update _localsetup/docs/ that reference the task), then create workflow docs if needed. Use lib/document_maintenance.sh when available.
Major task: Framework modifications, new tools, new features, significant config changes. Not: simple bug fixes, test-only changes.

---name: localsetup-framework-compliancedescription: Pre-task workflow, certainty assessment, context load, document status, testing, Git checkpoints, document maintenance. Use for framework modifications, PRDs, or any task that must follow checklist and checkpoints.--- # Framework compliance (pre-task, checkpoints, document maintenance) ## 0. MANDATORY PRE-TASK WORKFLOW (CRITICAL) Before executing ANY task: 1. **IDENTIFY TASK TYPE** - file_creation, code_modification, framework_modification, git_operation, etc. 2. **CHECK CORE RULES** (BLOCKS EXECUTION IF VIOLATED): Engine/user data separation; Git checkpoints after framework modifications; Markdown compatibility; Testing after changes; Backup management. 3. **ASSESS CERTAINTY** - HIGH/MEDIUM/LOW/CRITICAL LOW; if <70% lookup docs; if <50% on core rules get user confirmation. 4. **PRE-EXECUTION CHECKLIST** - Use `source lib/rule_enforcer_enhanced.sh && pre_execution_checklist "$task_type" "$task_description"` (when available). 5. **EXECUTE TASK** with rule compliance monitoring. 6. **POST-EXECUTION VERIFICATION** - Use `post_execution_verification "$task_type" "$task_context"`; verify checkpoints and backups. **Documentation lookup:** Check _localsetup/docs/, your platform's rules path (e.g. .cursor/rules/ on Cursor), _localsetup/config/rules_index.yaml. Never proceed with CRITICAL LOW certainty on core rules without user confirmation. ## 1. Context load and repo role - **VERIFY:** Context is loaded. If unsure, ask user to run `./_localsetup/tools/verify_context`. - **Repo role:** Framework lives in client repo at _localsetup/. Only modify local context (e.g. your platform's local rules, such as .cursor/rules/local-*.mdc on Cursor) or propose changes via PRD. See [REPO_AND_DATA_SEPARATION.md](../../docs/REPO_AND_DATA_SEPARATION.md). ## 6. Document status and testing - **Document status:** Before referencing any document, check status (ACTIVE/PROPOSAL/DRAFT/DEPRECATED/ARCHIVED). If PROPOSAL, do not assume implemented. Use `check_document_status()` or _localsetup/docs/DOCUMENT_INDEX.yaml. - **Testing:** Run _localsetup/tests/automated_test.sh after changes; maintain 100% test pass rate. ## 14. Git checkpoints (CRITICAL) - **MANDATORY:** Create Git checkpoints IMMEDIATELY after framework modifications. Use `_localsetup/tools/verify_rules` to verify. - **Checkpoint creation:** Stage and commit with messages like "Checkpoint: <operation> - <description>". Never commit user/repo-local data that should stay private. - **Rollback:** `git reset --hard <commit-hash>` (with confirmation). List: `git log --oneline`. ## 16. Document maintenance after major task - **Trigger:** After major task completion, user validation, and Git commit. - **Workflow:** Document scrub first (update _localsetup/docs/ that reference the task), then create workflow docs if needed. Use `lib/document_maintenance.sh` when available. - **Major task:** Framework modifications, new tools, new features, significant config changes. Not: simple bug fixes, test-only changes.

Frequently asked questions