[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DNS82AC359FVR7B6HSQD6D":3,"skill-same:01M7DNS82AC359FVR7B6HSQD6D":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M7DNS82AC359FVR7B6HSQD6D","ontoly-software-graph",null,"Use Ontoly's deterministic Software Graph, MCP server, and agent skills for architecture review, request tracing, impact analysis, and dependency analysis.","Hazek-dc\u002FPresensiGuru_FaceNet_EMAR","Hazek-dc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75208960?v=4","01M7DEQV5B4YGS86A81DYH81DR","Hazek","01M7DEQV5XP4TM0C6NTHXCXCHR",1,"MIT","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fontoly-software-graph\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ontoly-software-graph\ndescription: \"Use Ontoly's deterministic Software Graph, MCP server, and agent skills for architecture review, request tracing, impact analysis, and dependency analysis.\"\ncategory: development\nrisk: critical\nsource: community\nsource_repo: 0xsarwagya\u002Fontoly\nsource_type: community\ndate_added: \"2026-07-14\"\nauthor: 0xsarwagya\ntags: [software-graph, codebase-analysis, mcp, typescript, architecture, impact-analysis]\ntools: [claude, cursor, gemini, codex, antigravity]\nlicense: MIT\nlicense_source: \"https:\u002F\u002Fgithub.com\u002F0xsarwagya\u002Fontoly\u002Fblob\u002Fmain\u002FLICENSE\"\n---\n\n# Ontoly Software Graph\n\n## Overview\n\nOntoly builds a deterministic Software Graph from a TypeScript repository and exposes it through CLI queries, MCP capabilities, and agent skills. Use this skill when a coding agent needs evidence-backed codebase understanding before searching files directly.\n\nThis skill is an operating guide for the public Ontoly project. It does not contain compiler logic; all software understanding should come from Ontoly's generated graph, semantic model, query engine, and MCP server.\n\n## When to Use This Skill\n\n- Use when the user asks for repository architecture, module ownership, or onboarding help.\n- Use when tracing a request, route, controller, service, provider, dependency, or call chain.\n- Use when estimating impact for removing, renaming, or refactoring a symbol, module, package, route, or service.\n- Use when reviewing dependency topology, circular imports, dead code, configuration usage, or environment variables.\n- Use when the user explicitly wants Ontoly, Software Graph, MCP, graph validation, semantic coverage, or agent skills.\n\n## How It Works\n\n### Step 1: Verify Ontoly Is Available\n\nCheck whether the repository already has Ontoly outputs such as `.ontoly\u002F`, `SoftwareGraph.json`, validation reports, or documented Ontoly scripts. If the `ontoly` command is unavailable, ask the user whether to install or use the repository's documented package manager command.\n\nRecommended local checks:\n\n```bash\nontoly --help\nfind . -maxdepth 3 \\( -name \"SoftwareGraph.json\" -o -name \".ontoly\" \\) -print\n```\n\n### Step 2: Build or Refresh the Graph\n\nOnly run a graph build in the repository the user asked about. Tell the user that graph generation may create local Ontoly artifacts before running it.\n\n```bash\nontoly build .\n```\n\nIf the project documents a different command, prefer the documented command over guessing.\n\n### Step 3: Check Trust, Diagnostics, and Coverage\n\nBefore answering architectural questions, inspect Ontoly diagnostics, graph statistics, trust, and semantic coverage. Treat unresolved imports, low trust, missing framework detection, or graph validation failures as answer constraints.\n\nUse the CLI or MCP capabilities exposed by the installed Ontoly version. Prefer structured graph queries over text search.\n\n### Step 4: Use Ontoly MCP Capabilities\n\nStart or connect to the Ontoly MCP server when the host supports MCP:\n\n```bash\nontoly mcp\n```\n\nUse capabilities such as architecture summaries, dependency analysis, request tracing, impact analysis, configuration lookup, framework reports, dead-code analysis, and graph validation when available.\n\n### Step 5: Answer With Evidence\n\nEvery answer should include:\n\n- The Ontoly capability or query used.\n- The node, edge, route, package, or diagnostic evidence that supports the answer.\n- A confidence statement derived from graph evidence.\n- Any known limitations caused by missing graph regions or diagnostics.\n\n### Step 6: Fall Back Gracefully\n\nOnly inspect repository files directly when Ontoly cannot answer, the graph is missing, diagnostics make the graph untrustworthy for the question, or the user asks for source-level verification. When falling back, explain which graph evidence was insufficient.\n\n## Examples\n\n### Architecture Review\n\nUser asks: \"Explain this repository.\"\n\nWorkflow:\n\n1. Verify or build the Ontoly graph.\n2. Check graph trust, diagnostics, detected frameworks, packages, modules, services, routes, and largest dependency hubs.\n3. Use Ontoly's architecture summary or equivalent query.\n4. Report the architecture with graph evidence and confidence.\n\n### Request Tracing\n\nUser asks: \"Trace the login flow.\"\n\nWorkflow:\n\n1. Search graph nodes for authentication routes and controllers.\n2. Trace route-to-controller-to-service-to-repository relationships.\n3. Include unresolved edges or missing relationships as limitations.\n4. Avoid opening source files unless the graph cannot identify the flow.\n\n### Impact Analysis\n\nUser asks: \"What breaks if I remove UserRepository?\"\n\nWorkflow:\n\n1. Locate the graph node for `UserRepository`.\n2. Query callers, consumers, dependency injection edges, modules, routes, and packages that reference it.\n3. Separate direct dependents from transitive impact.\n4. Include confidence based on explicit graph relationships.\n\n## Best Practices\n\n- Prefer Ontoly graph queries before grep, AST parsing, or broad file search.\n- Keep graph evidence separate from inference.\n- Treat diagnostics as part of the answer, not as noise.\n- Use exact node IDs, route paths, package names, and relationship names when available.\n- Rebuild the graph after large user changes before making claims about current architecture.\n- Keep fallbacks narrow and explain why they were needed.\n\n## Limitations\n\n- Ontoly does not replace compiler, test, or runtime validation.\n- Graph quality depends on the Ontoly version, supported language frontend, repository setup, and diagnostics.\n- Missing or partial framework detection lowers confidence for framework-specific answers.\n- Do not claim a relationship exists unless it is present in the graph or clearly labeled as an inference.\n- Stop and ask for clarification if the repository path, target graph, or requested analysis scope is ambiguous.\n\n## Security & Safety Notes\n\n- Run Ontoly only on repositories the user is authorized to analyze.\n- Do not send graph files, source code, environment variables, diagnostics, or repository metadata to external services unless the user explicitly requests it.\n- Treat environment-variable nodes, configuration nodes, and diagnostics as potentially sensitive.\n- Graph generation is local analysis but can create files such as graph output, diagnostics, indexes, or caches inside the repository.\n- Do not execute project build scripts, package installation, or network commands unless they are documented by the repository or approved by the user.\n\n## Common Pitfalls\n\n- **Problem:** Answering from file search even though the graph already contains the relationship.\n  **Solution:** Query Ontoly first and use file inspection only as a fallback.\n\n- **Problem:** Reporting low-confidence inference as a graph fact.\n  **Solution:** Label the claim as inferred and cite the supporting graph evidence separately.\n\n- **Problem:** Ignoring diagnostics.\n  **Solution:** Include graph validation and compiler diagnostics when they affect confidence.\n\n## Related Skills\n\n- `@developer-onboarding` - Use for broad onboarding when Ontoly is unavailable.\n- `@sdk-dx` - Use for SDK design and developer experience reviews after Ontoly identifies public APIs.\n- `@api-onboarding` - Use for API-specific onboarding when route and operation evidence is available.\n","# Ontoly Software Graph\n\n## Overview\n\nOntoly builds a deterministic Software Graph from a TypeScript repository and exposes it through CLI queries, MCP capabilities, and agent skills. Use this skill when a coding agent needs evidence-backed codebase understanding before searching files directly.\n\nThis skill is an operating guide for the public Ontoly project. It does not contain compiler logic; all software understanding should come from Ontoly's generated graph, semantic model, query engine, and MCP server.\n\n## When to Use This Skill\n\n- Use when the user asks for repository architecture, module ownership, or onboarding help.\n- Use when tracing a request, route, controller, service, provider, dependency, or call chain.\n- Use when estimating impact for removing, renaming, or refactoring a symbol, module, package, route, or service.\n- Use when reviewing dependency topology, circular imports, dead code, configuration usage, or environment variables.\n- Use when the user explicitly wants Ontoly, Software Graph, MCP, graph validation, semantic coverage, or agent skills.\n\n## How It Works\n\n### Step 1: Verify Ontoly Is Available\n\nCheck whether the repository already has Ontoly outputs such as `.ontoly\u002F`, `SoftwareGraph.json`, validation reports, or documented Ontoly scripts. If the `ontoly` command is unavailable, ask the user whether to install or use the repository's documented package manager command.\n\nRecommended local checks:\n\n```bash\nontoly --help\nfind . -maxdepth 3 \\( -name \"SoftwareGraph.json\" -o -name \".ontoly\" \\) -print\n```\n\n### Step 2: Build or Refresh the Graph\n\nOnly run a graph build in the repository the user asked about. Tell the user that graph generation may create local Ontoly artifacts before running it.\n\n```bash\nontoly build .\n```\n\nIf the project documents a different command, prefer the documented command over guessing.\n\n### Step 3: Check Trust, Diagnostics, and Coverage\n\nBefore answering architectural questions, inspect Ontoly diagnostics, graph statistics, trust, and semantic coverage. Treat unresolved imports, low trust, missing framework detection, or graph validation failures as answer constraints.\n\nUse the CLI or MCP capabilities exposed by the installed Ontoly version. Prefer structured graph queries over text search.\n\n### Step 4: Use Ontoly MCP Capabilities\n\nStart or connect to the Ontoly MCP server when the host supports MCP:\n\n```bash\nontoly mcp\n```\n\nUse capabilities such as architecture summaries, dependency analysis, request tracing, impact analysis, configuration lookup, framework reports, dead-code analysis, and graph validation when available.\n\n### Step 5: Answer With Evidence\n\nEvery answer should include:\n\n- The Ontoly capability or query used.\n- The node, edge, route, package, or diagnostic evidence that supports the answer.\n- A confidence statement derived from graph evidence.\n- Any known limitations caused by missing graph regions or diagnostics.\n\n### Step 6: Fall Back Gracefully\n\nOnly inspect repository files directly when Ontoly cannot answer, the graph is missing, diagnostics make the graph untrustworthy for the question, or the user asks for source-level verification. When falling back, explain which graph evidence was insufficient.\n\n## Examples\n\n### Architecture Review\n\nUser asks: \"Explain this repository.\"\n\nWorkflow:\n\n1. Verify or build the Ontoly graph.\n2. Check graph trust, diagnostics, detected frameworks, packages, modules, services, routes, and largest dependency hubs.\n3. Use Ontoly's architecture summary or equivalent query.\n4. Report the architecture with graph evidence and confidence.\n\n### Request Tracing\n\nUser asks: \"Trace the login flow.\"\n\nWorkflow:\n\n1. Search graph nodes for authentication routes and controllers.\n2. Trace route-to-controller-to-service-to-repository relationships.\n3. Include unresolved edges or missing relationships as limitations.\n4. Avoid opening source files unless the graph cannot identify the flow.\n\n### Impact Analysis\n\nUser asks: \"What breaks if I remove UserRepository?\"\n\nWorkflow:\n\n1. Locate the graph node for `UserRepository`.\n2. Query callers, consumers, dependency injection edges, modules, routes, and packages that reference it.\n3. Separate direct dependents from transitive impact.\n4. Include confidence based on explicit graph relationships.\n\n## Best Practices\n\n- Prefer Ontoly graph queries before grep, AST parsing, or broad file search.\n- Keep graph evidence separate from inference.\n- Treat diagnostics as part of the answer, not as noise.\n- Use exact node IDs, route paths, package names, and relationship names when available.\n- Rebuild the graph after large user changes before making claims about current architecture.\n- Keep fallbacks narrow and explain why they were needed.\n\n## Limitations\n\n- Ontoly does not replace compiler, test, or runtime validation.\n- Graph quality depends on the Ontoly version, supported language frontend, repository setup, and diagnostics.\n- Missing or partial framework detection lowers confidence for framework-specific answers.\n- Do not claim a relationship exists unless it is present in the graph or clearly labeled as an inference.\n- Stop and ask for clarification if the repository path, target graph, or requested analysis scope is ambiguous.\n\n## Security & Safety Notes\n\n- Run Ontoly only on repositories the user is authorized to analyze.\n- Do not send graph files, source code, environment variables, diagnostics, or repository metadata to external services unless the user explicitly requests it.\n- Treat environment-variable nodes, configuration nodes, and diagnostics as potentially sensitive.\n- Graph generation is local analysis but can create files such as graph output, diagnostics, indexes, or caches inside the repository.\n- Do not execute project build scripts, package installation, or network commands unless they are documented by the repository or approved by the user.\n\n## Common Pitfalls\n\n- **Problem:** Answering from file search even though the graph already contains the relationship.\n  **Solution:** Query Ontoly first and use file inspection only as a fallback.\n\n- **Problem:** Reporting low-confidence inference as a graph fact.\n  **Solution:** Label the claim as inferred and cite the supporting graph evidence separately.\n\n- **Problem:** Ignoring diagnostics.\n  **Solution:** Include graph validation and compiler diagnostics when they affect confidence.\n\n## Related Skills\n\n- `@developer-onboarding` - Use for broad onboarding when Ontoly is unavailable.\n- `@sdk-dx` - Use for SDK design and developer experience reviews after Ontoly identifies public APIs.\n- `@api-onboarding` - Use for API-specific onboarding when route and operation evidence is available.\n",{"name":5,"risk":24,"tags":25,"tools":32,"author":38,"source":39,"license":15,"category":40,"date_added":41,"description":7,"source_repo":42,"source_type":39,"license_source":43},"critical",[26,27,28,29,30,31],"software-graph","codebase-analysis","mcp","typescript","architecture","impact-analysis",[33,34,35,36,37],"claude","cursor","gemini","codex","antigravity","0xsarwagya","community","development","2026-07-14","0xsarwagya\u002Fontoly","https:\u002F\u002Fgithub.com\u002F0xsarwagya\u002Fontoly\u002Fblob\u002Fmain\u002FLICENSE","main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Fontoly-software-graph",0,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR","https:\u002F\u002Fgithub.com\u002FHazek-dc","2026-10-22 08:36:44",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill ontoly-software-graph",{"tool":57,"command":58},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill ontoly-software-graph",{"tool":60,"command":61},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill ontoly-software-graph","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fontoly-software-graph\u002FSKILL.md",true,[],[66,73,80,87,94,101],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7DS6GGYRZAYD33PFPS8Z2T3","testing-best-practices","Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7DS6BC3AW7HTPRHE2TTVKWM","tailwindcss-development","Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex\u002Fgrid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3\u002Fv4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML\u002FCSS component, CSS file audits, build tool configuration, and vanilla CSS.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftailwindcss-development\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7DS66GE6B11MYJDVC74HXM4","laravel-best-practices","Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Flaravel-best-practices\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7DS5ZW717DMS6P1E90AQCKV","infer-conventions","Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai\u002Frules`, resolve mixed or conflicting patterns (e.g. \"are we using Form Requests or inline validation?\"), or onboard agents and teammates to \"how we do things here\". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai\u002Frules` files by hand.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finfer-conventions\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7DS5W12RGCVJTFQJ1N0GB8E","inertia-react-development","Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using \u003CLink>, \u003CForm>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finertia-react-development\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7DS5PVDPMPCWSK2RXPDC9BB","deploying-to-cloud","Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Fdeploying-to-cloud\u002FSKILL.md",[],[]]