تشغيل أي مهارة في Manus بنقرة واحدة

ابدأ الآن

grimp-architecture

النجوم١

التفرعات٠

آخر تحديث١٩ يناير ٢٠٢٦ في ١٧:٥٠

Explore Python import graphs and enforce layered architecture using grimp.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

charlieyou

charlieyou/cyai

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

مستكشف الملفات

2 ملفات

SKILL.md

readonly

name	grimp-architecture
description	Explore Python import graphs and enforce layered architecture using grimp.

Grimp Architecture Exploration

Use this skill when the user wants to explore Python module boundaries, investigate dependency flow, or enforce layered architecture with grimp.

Setup

Create the venv and install grimp (requires Python 3.12):

uv venv ~/.agents/skills/grimp-architecture/.venv --python 3.12
uv pip install grimp --python ~/.agents/skills/grimp-architecture/.venv/bin/python

Quick Start

# Shorthand
GRIMP=~/.agents/skills/grimp-architecture/.venv/bin/python\ ~/.agents/skills/grimp-architecture/scripts/grimp_cli.py

Explore the graph (fan-in/out, top-level structure):
```
$GRIMP explore mypackage
```

Trace a boundary leak (shortest import chain):

$GRIMP path mypackage.validation mypackage.orchestrator

Optional layer check (ordered high -> low):

$GRIMP layers --layer mypackage.api --layer mypackage.domain --layer mypackage.infra

Incremental enforcement (baseline + diff):

$GRIMP layers --layer mypackage.api --layer mypackage.domain --layer mypackage.infra --json > .grimp-baseline.json
$GRIMP diff --baseline .grimp-baseline.json --layer mypackage.api --layer mypackage.domain --layer mypackage.infra

Commands

explore <package> [--top N]: summarize structure, fan-in/out, and child packages.
path <importer> <imported>: shortest import chain between modules/packages.
layers --layer ...: find illegal dependencies for an ordered layer list.
diff --baseline ... --layer ...: fail only on new layer violations.

All commands accept --include-external to include external packages in the graph.

Guidance

Explore first: run explore before defining layers so you understand how the code is organized.
Use path tracing to confirm suspicious dependencies before reporting them.
Layer checks are optional unless the repo already defines layers or the review clearly proposes them.
Baseline + diff is the safest way to enforce architecture incrementally in large codebases.

Packaging Expectations

Grimp needs the project to be importable by package name (not file paths).

Use a normal package layout with __init__.py files.
Run from the project root — scripts auto-detect packages in the current directory.
For src/ layouts, set PYTHONPATH=src or install the project.
Editable installs are fine for local exploration.

Sanity check:

python -c "import mypackage; print(mypackage.__file__)"

Common options:

uv sync
uv pip install -e .
PYTHONPATH=src $GRIMP explore mypackage  # for src/ layouts

Notes

Python 3.12 is required - grimp has compatibility issues with Python 3.14+.
The skill venv at ~/.agents/skills/grimp-architecture/.venv has grimp pre-installed.
For advanced grimp features (closed layers, non-independent siblings, containers), use a custom Python snippet.

المزيد من هذا المستودع

نفس المستودع

beads

charlieyou/cyai

Manages issues via the br CLI (beads), a local-first tracker stored in .beads/ (SQLite + JSONL). Use when capturing issues, finding ready work, claiming issues, managing dependencies, or syncing changes. Triggers: "br", "beads", "issue tracking".

2026-07-211

prompt-engineering

charlieyou/cyai

Review, rewrite, and debug LLM prompts. Use when asked to: (1) improve an existing prompt, (2) design a new system or developer prompt, (3) add few-shot examples, (4) define output schemas and success criteria, (5) diagnose prompt failures from transcripts. Not for: model policy workarounds, producing domain answers without context, or guaranteeing model-specific behavior.

2026-05-121

creating-mala-yaml

charlieyou/cyai

Creates or updates mala.yaml project configuration files for the local mala orchestrator. Use when asked to initialize, generate, write, edit, validate, fix, or explain a mala.yaml config, including presets, commands, coverage, evidence checks, validation triggers, or review settings.

2026-04-301

simplifying-code

charlieyou/cyai

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise. Triggers: simplify, refine, clean up code.

2026-03-081

browser-use

charlieyou/cyai

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, or extract information from web pages.

2026-01-251

querying-dune

charlieyou/cyai

Executes SQL queries on Dune Analytics and writes results as CSV to /tmp. Use when the user needs blockchain data from Dune or wants to run a saved Dune query by ID. Triggers: "dune query", "dune sql", "query dune", "blockchain data"

2026-01-201

name	grimp-architecture
description	Explore Python import graphs and enforce layered architecture using grimp.

Grimp Architecture Exploration

Use this skill when the user wants to explore Python module boundaries, investigate dependency flow, or enforce layered architecture with grimp.

Setup

Create the venv and install grimp (requires Python 3.12):

uv venv ~/.agents/skills/grimp-architecture/.venv --python 3.12
uv pip install grimp --python ~/.agents/skills/grimp-architecture/.venv/bin/python

Quick Start

# Shorthand
GRIMP=~/.agents/skills/grimp-architecture/.venv/bin/python\ ~/.agents/skills/grimp-architecture/scripts/grimp_cli.py

Explore the graph (fan-in/out, top-level structure):
```
$GRIMP explore mypackage
```

Trace a boundary leak (shortest import chain):

$GRIMP path mypackage.validation mypackage.orchestrator

Optional layer check (ordered high -> low):

$GRIMP layers --layer mypackage.api --layer mypackage.domain --layer mypackage.infra

Incremental enforcement (baseline + diff):

$GRIMP layers --layer mypackage.api --layer mypackage.domain --layer mypackage.infra --json > .grimp-baseline.json
$GRIMP diff --baseline .grimp-baseline.json --layer mypackage.api --layer mypackage.domain --layer mypackage.infra

Commands

explore <package> [--top N]: summarize structure, fan-in/out, and child packages.
path <importer> <imported>: shortest import chain between modules/packages.
layers --layer ...: find illegal dependencies for an ordered layer list.
diff --baseline ... --layer ...: fail only on new layer violations.

All commands accept --include-external to include external packages in the graph.

Guidance

Explore first: run explore before defining layers so you understand how the code is organized.
Use path tracing to confirm suspicious dependencies before reporting them.
Layer checks are optional unless the repo already defines layers or the review clearly proposes them.
Baseline + diff is the safest way to enforce architecture incrementally in large codebases.

Packaging Expectations

Grimp needs the project to be importable by package name (not file paths).

Use a normal package layout with __init__.py files.
Run from the project root — scripts auto-detect packages in the current directory.
For src/ layouts, set PYTHONPATH=src or install the project.
Editable installs are fine for local exploration.

Sanity check:

python -c "import mypackage; print(mypackage.__file__)"

Common options:

uv sync
uv pip install -e .
PYTHONPATH=src $GRIMP explore mypackage  # for src/ layouts

Notes

Python 3.12 is required - grimp has compatibility issues with Python 3.14+.
The skill venv at ~/.agents/skills/grimp-architecture/.venv has grimp pre-installed.
For advanced grimp features (closed layers, non-independent siblings, containers), use a custom Python snippet.