Ijfw Summarize
Generate optimized project context from codebase scan. Trigger: new project, no CLAUDE.md, /ijfw-summarize
Install
npx skills add FerroxLabs/wayland-core --skill ijfw-summarizegit clone --depth 1 https://github.com/FerroxLabs/wayland-core.git /tmp/wayland-core
mkdir -p ~/.claude/skills
cp -r /tmp/wayland-core/crates/wayland-ijfw/snapshots/ijfw-source/claude/skills/ijfw-summarize ~/.claude/skills/ijfw-summarizePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
Scan the codebase and generate an optimized project context file. ## Process 1. Read: package.json, tsconfig.json, Cargo.toml, pyproject.toml, go.mod, Dockerfile, docker-compose.yml, .env.example, Makefile -- whatever exists. 2. Scan: directory structure (2 levels deep), test framework, linter config, CI config. 3. Detect: language, framework, database, ORM, auth approach, deployment target. 4. Identify: key directories, entry points, API route patterns, shared utilities. ## Output Write a CLAUDE.md (or platform equivalent) with: ```markdown # Project Context Stack: <framework> / <language> / <database> Architecture: <pattern -- monolith, microservices, serverless, etc.> Entry: <main entry point(s)> Tests: <framework + command to run> Lint: <tool + command> ## Structure <key directories and their purpose, 1 line each> ## Patterns <established code patterns to follow, 1 line each> ## Key Files <important files a new contributor should know about> ``` Rules: - Max 50 lines. This loads every session. - No boilerplate explanations. Just facts. - If uncertain about a pattern, omit it -- don't guess.
Details
- Skill name
ijfw-summarize- Repository
- FerroxLabs/wayland-core
- Path
crates/wayland-ijfw/snapshots/ijfw-source/claude/skills/ijfw-summarize/SKILL.md- License
- Apache-2.0
- Repo updated
- 3 November 2026
FAQ
What does the Ijfw Summarize skill do?
Generate optimized project context from codebase scan. Trigger: new project, no CLAUDE.md, /ijfw-summarize
How do I install the Ijfw Summarize skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add FerroxLabs/wayland-core --skill ijfw-summarize. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Ijfw Summarize popular?
It lives in FerroxLabs/wayland-core, which has 43 GitHub stars and 17 forks.
Related skills
Ijfw Agents Md
43FerroxLabs/wayland-core
Maintain canonical AGENTS.md (open spec). Trigger: 'agents.md', 'update AGENTS.md', or auto-fired by ijfw-team after agent generation.
Ijfw Auto Memorize
43FerroxLabs/wayland-core
Session-end auto-extraction of lessons, errors, fixes, and user feedback into structured memory. Fires at session end. Requires consent on first run.
Ijfw Commit
43FerroxLabs/wayland-core
Terse conventional commits. Trigger: commit, git commit, /ijfw-commit
Barcode Scanning
49dynamics365ninja/d365fo-cli
Barcodes and scanner input in D365FO — printing vs scanning are unrelated code paths, GS1-128 application identifiers, item-barcode resolution, and where the platform parses a scan for you. Invoke when the user mentions barcodes, GS1, GTIN, SSCC, scanning, scanners, item barcodes, or barcode setup.
Ijfw Cross Audit
43FerroxLabs/wayland-core
Generate a cross-platform multi-model audit (Trident) on a diff, brief, or artifact. Trigger: 'cross audit', 'Trident', 'second opinion', 'check with other models', 'cross-check this', 'get another perspective', /cross-audit
Build Error Triage
49dynamics365ninja/d365fo-cli
Turn a D365FO compiler, best-practice, or runtime error into the specific fix it calls for. Invoke when the user pastes a build log, an xppc message, a BP violation, or an infolog stack trace and asks what it means or how to fix it.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.