understand-project
Skill459 starsChanged 3 months agoMITView on GitHub
Ground a feature or fix in existing code before planning or building — find a similar pattern, identify reusable assets, map the touch surface. Internal helper invoked by feat / fix (both modes) — not meant to be run on its own.
Files
Ground every plan and implementation in code that already exists. A plan that says "follows the same pattern as app/components/edit/DocumentEdit.svelte" beats one describing an abstraction in the abstract — the executor gets low cognitive load and a working reference. This is the method; the calling skill says what to build.
Steps
- Learn the layout that applies. App code is under
app/:.sveltescreens/components/modals live inapp/components/<feature>/(feature dirs:camera,edit,list,ocr,pdf,pkpass,qrcode,security,settings,view,common,widgets); domain logic lives in service singletons underapp/services/(documents.ts,sync.ts,ocr.ts,security.ts, …); data models inapp/models/; helpers inapp/utils/,app/helpers/,app/transformers/; strings inapp/i18n/; SCSS themes inapp/themes/. Platform splits use.android.ts/.ios.ts. - Find a similar existing implementation. Glob/Grep for a
.sveltecomponent or a service that solves a comparable problem. Read 1-2 end-to-end so you can point at them by path. - Identify reusable assets — existing components in
app/components/common/andapp/components/widgets/, svelte stores (app/utils/svelte/store.ts), service singletons, models, and utils/helpers. Reuse these by name rather than inventing new ones. - Map the touch surface — every file, component, service, model, i18n key that needs to change. Trace data flow and callers (service singletons are shared, so a change ripples) so nothing is missed.
- Check third-party libraries — when a library is involved (
@nativescript-community/*,@akylas/*, svelte-native, sqlite/kiss-orm, …), use Context7 for version-matched docs before assuming an API.
Bias
Pick the simplest, cleanest solution: reuse existing patterns/components/hooks, fewest files touched, smallest new surface. If a clever approach and a boring approach reach the same outcome, choose the boring one.
Other versions4 projects use a version of this.
Word for word · 1
- Akylas/OSS-DocumentScanner★ 2.6k100% same
Edited · 0
None found.
Wrote their own version · 3
- yylo-dev/yylo★ 66same name
- hamburger-os/PraxFlow★ 1same name
- Omerfaruk-aydn/Agent_OS★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- branch-checkSkill
- commitSkill
- writing-great-skillsSkill
- documentSkill
- featSkill
- fixSkill
- grill-meSkill
- investigate-contractSkill
- open-prSkill
- save-plan-to-githubSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.