메뉴
Read-only design scanner. Finds abstraction, MI, and generics improvement opportunities in Eiffel libraries. Produces structured report. Use with /eiffel.design-scan command.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/simple-eiffel/eiffel-spec-kit --skill eiffel-design-scan명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
SOC 직업 분류 기준
Extract shared behavior into deferred class abstractions following ISE EiffelBase patterns. Each abstraction level adds contracts, not implementation. Use with /eiffel.abstract command.
Convert concrete-typed Eiffel classes to use generic parameters with proper constraints following ISE EiffelBase patterns. Use with /eiffel.generify command.
Apply Eiffel multiple inheritance with role-based parents. Uses feature adaptation (rename/redefine/undefine/select) to resolve conflicts. Use with /eiffel.mi command.
| name | eiffel-design-scan |
| description | Read-only design scanner. Finds abstraction, MI, and generics improvement opportunities in Eiffel libraries. Produces structured report. Use with /eiffel.design-scan command. |
| allowed-tools | Read, Grep, Glob, Bash, Task |
Purpose: Scan an Eiffel library to discover design improvement opportunities in three categories: missing abstractions, multiple inheritance candidates, and generics candidates. This is READ-ONLY — no source files are modified.
/eiffel.design-scan <library-path>
Example:
/eiffel.design-scan d:\prod\simple_sorter
If no path provided, ask user: "Which library? Provide the full path (e.g., d:\prod\simple_sorter)"
<library-path>/
├── .eiffel-workflow/
│ └── evidence/
│ └── design-scan.md ← OUTPUT (the only file written)
├── src/
│ └── *.e ← SCANNED (read-only)
├── test/
│ └── *.e ← SCANNED (read-only)
└── <library>.ecf ← SCANNED (read-only)
These principles from ISE EiffelBase guide every finding:
[G -> COMPARABLE] means "this class needs ordering"Read every .e file in <library-path>/src/. For each class, record:
Build a mental model of the class hierarchy and feature landscape.
Efficiency: Use Grep to locate structural elements quickly before deep-reading:
# Find all class declarations
grep -rn "^class\|^deferred class\|^expanded class" <library-path>/src/
# Find all inherit clauses
grep -rn "^inherit" <library-path>/src/
# Find all generic parameters
grep -rn "class.*\[" <library-path>/src/
# Find deferred features
grep -rn "deferred$\|deferred " <library-path>/src/
Scan for these patterns:
A1: Duplicate Feature Signatures
A2: Deep Inheritance Chains
A3: Template Method Candidates
< generates <=, >, >=)A4: Missing Contracts on Shared Behavior
For each finding, record:
Category: A1/A2/A3/A4
Classes: [list]
Features: [list with line numbers]
Description: [what the abstraction would capture]
Effort: [number of features to extract]
Scan for these patterns:
M1: Missing ITERABLE
new_cursor for across loop compatibilityM2: Duplicated Cross-Cutting Concerns
M3: Missing Standard Parents
< but don't inherit COMPARABLEhash_code but don't inherit HASHABLEout but could benefit from CUSTOM_OUTPUTM4: Monolithic Classes
For each finding, record:
Category: M1/M2/M3/M4
Class: [target class]
Proposed Parent: [parent class name and role]
Features Affected: [list with line numbers]
Conflicts: [potential name clashes to resolve]
Scan for these patterns:
G1: Concrete Types Where Generic Would Be Safer
ANY for element typesG2: Missing Constraints on Existing Generics
[G] where [G -> COMPARABLE] needed because < is used on G[G] where [G -> HASHABLE] needed because hash_code is called on Gdetachable separate for SCOOP compatibilityG3: like Current Candidates
like CurrentG4: Type Parameter Extraction
For each finding, record:
Category: G1/G2/G3/G4
Class: [target class]
Current Type: [concrete type being used]
Proposed Parameter: [G/K/V with constraint]
Features Affected: [list with line numbers]
Client Impact: [files that would need updating]
Create directory if needed:
mkdir -p <library-path>/.eiffel-workflow/evidence
Write <library-path>/.eiffel-workflow/evidence/design-scan.md:
# Design Scan: <library-name>
# Date: [timestamp]
# Classes scanned: [count]
# Source files: [count]
## Summary
| Category | Findings | High | Medium | Low |
|----------|----------|------|--------|-----|
| Abstraction | [n] | [n] | [n] | [n] |
| MI | [n] | [n] | [n] | [n] |
| Generics | [n] | [n] | [n] | [n] |
| **Total** | **[n]** | **[n]** | **[n]** | **[n]** |
## Findings
| # | Priority | Category | Classes | Opportunity | Effort | Suggested Skill |
|---|----------|----------|---------|-------------|--------|-----------------|
| 1 | HIGH | abstract | A, B | Extract deferred X | 3 features | /eiffel.abstract |
| 2 | MEDIUM | mi | C | Add ITERABLE parent | 1 feature | /eiffel.mi |
| 3 | LOW | generics | D | Parameterize on G | 5 features | /eiffel.generify |
## Detailed Findings
### Finding 1: [title]
**Priority:** HIGH
**Category:** abstract
**Classes:** [class names with file paths]
**Description:** [what the opportunity is and why it matters]
**Evidence:**
- [class]:line [n]: [feature signature]
- [class]:line [n]: [feature signature]
**Suggested Action:** /eiffel.abstract targeting [classes]
**Effort:** [n] features to extract
[... repeat for each finding ...]
## Recommended Order
1. [Finding #] — [why first: highest impact / unblocks others]
2. [Finding #] — [why second]
3. ...
Design scan COMPLETE for: <library-path>
Report: <library-path>/.eiffel-workflow/evidence/design-scan.md
Findings: [n] total ([n] HIGH, [n] MEDIUM, [n] LOW)
- Abstraction opportunities: [n]
- MI opportunities: [n]
- Generics opportunities: [n]
Do NOT blindly list next steps. The report speaks for itself — the user can read it and decide what to act on. Only mention a specific skill if the user asks "what now?"
This skill focuses ONLY on: <library-path>
DO NOT:
DO:
<library-path>/.eiffel-workflow/skill-improvements.md — do NOT modify skills mid-workflow