[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DFRNGJH8X41SDAC0BQV307":3,"skill-same:01M7DFRNGJH8X41SDAC0BQV307":63},{"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":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M7DFRNGJH8X41SDAC0BQV307","ax-extract-workflow",null,"Reconstruct workflow behind a past coding-agent artifact using local ax sessions\u002Fcommits\u002Fskills\u002Ftool traces. Use when asked how X was built.","Hazek-dc\u002FPresensiGuru_FaceNet_EMAR","Hazek-dc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75208960?v=4","01M7DEQV5B4YGS86A81DYH81DR","Hazek","01M7DEQV5XP4TM0C6NTHXCXCHR",1,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fax-extract-workflow\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ax-extract-workflow\ndescription: \"Reconstruct workflow behind a past coding-agent artifact using local ax sessions\u002Fcommits\u002Fskills\u002Ftool traces. Use when asked how X was built.\"\ncategory: development\nrisk: safe\nsource: community\nsource_repo: Necmttn\u002Fax\nsource_type: community\ndate_added: \"2026-06-21\"\nauthor: Necmttn\ntags: [ai-coding, workflow-reconstruction, session-analysis, observability]\ntools: [claude, cursor, gemini, codex-cli]\nlicense: \"AGPL-3.0-only\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002FNecmttn\u002Fax\u002Fblob\u002Fmain\u002FLICENSE\"\n---\n\n# ax Extract Workflow\n\n## Overview\n\nUse this skill to reconstruct the workflow behind a past coding-agent artifact:\na shipped feature, PR, demo, refactor, report, or other concrete result. It uses\nthe local `ax` graph to connect commits, sessions, turns, skills, and tool traces\ninto a short \"how this got made\" narrative.\n\n`ax` must be installed, available on `PATH`, and able to reach its local database.\nIf ax cannot connect to its DB, report the connection failure and stop instead of\nguessing from memory.\n\n## When to Use This Skill\n\n- Use when the user asks \"how did we build X?\", \"what made X work?\", or \"extract the workflow behind this artifact.\"\n- Use when the anchor is a commit SHA, date, feature name, PR, session, or repo-local artifact.\n- Use when the user wants the sequence of agent skills, prompts, commands, decisions, and checks that led to a result.\n- Do not use for a generic activity summary; use normal session listing instead.\n\n## How It Works\n\n### Step 1: Resolve the Anchor\n\nIdentify the best anchor from the user's request:\n\n- Commit SHA: use it directly.\n- Date or date range: inspect sessions around the date.\n- Topic, feature, or artifact name: search recall for related turns, commits, and skills.\n- \"This repo recently\": list recent sessions for the current repo.\n\n```bash\nax recall \"live ingest dashboard\" --sources=turn,commit,skill --scope=here\nax sessions near abc1234 --json\nax sessions around 2026-06-15 --days=3 --json\nax sessions here --days=14\n```\n\nThese commands are read-only inspection commands.\n\n### Step 2: Pick Relevant Sessions\n\nChoose the few sessions most likely to explain the artifact. Prefer sessions\nthat mention the artifact, touch related files, include relevant commits, or have\nskills and tool calls that match the work.\n\nIf several candidates are plausible, show the user the candidates and ask which\none to inspect.\n\n### Step 3: Inspect the Session Trail\n\nOpen each selected session and look for:\n\n- skills used and their order\n- user steering points and clarified constraints\n- files, tests, and commands that changed the direction of the work\n- subagent or tool traces that produced key evidence\n- verification steps before the result was considered done\n\n```bash\nax sessions show \u003Csession-id> --json\nax sessions show \u003Csession-id> --by-role\nax recall \"specific keyword from the artifact\" --sources=turn,commit --scope=here\n```\n\n### Step 4: Write the Reconstruction\n\nReturn the result inline unless the user asks for a file. Keep it short and\nevidence-grounded:\n\n1. Anchor: the date, commit, feature, or artifact you resolved.\n2. Ordered workflow: 4-8 steps showing the skill or action and what it produced.\n3. Key decisions: the user or agent choices that changed the path.\n4. Verification: tests, reviews, checks, or manual evidence.\n5. Reproducer brief: the compact recipe for doing similar work again.\n\nUse session IDs, commit SHAs, and file paths as citations when available.\n\n## Examples\n\n### Reconstruct a Feature from a Commit\n\n```bash\nax sessions near 8f31c2a --json\nax sessions show \u003Csession-id> --by-role\nax sessions show \u003Csession-id> --json\n```\n\nOutput shape:\n\n```text\nAnchor: 8f31c2a, live ingest dashboard\n\nWorkflow:\n1. Problem framing -> narrowed the failure to stale dashboard polling.\n2. Session recall -> found the earlier ingest-stream design and constraints.\n3. Implementation -> wired the server event bus and browser subscription.\n4. Verification -> ran typecheck and refreshed the dashboard locally.\n\nReproducer brief:\nStart from the failing artifact, find nearby sessions, inspect role-grouped\nskills, then summarize the smallest ordered path from framing to verification.\n```\n\n### Reconstruct Work Around a Date\n\n```bash\nax sessions around 2026-06-15 --days=2 --json\nax recall \"otel receiver\" --sources=turn,commit,skill --scope=here\n```\n\nUse this when the user remembers when the work happened but not the commit.\n\n## Best Practices\n\n- Start from the most concrete anchor available: SHA beats date, date beats vague topic.\n- Treat ax as the source of truth; do not invent missing skills, costs, commands, or decisions.\n- Quote sparingly and only when a user decision or command matters to the reconstruction.\n- Keep private transcript details private; summarize rather than dumping logs.\n- Separate \"what happened\" from \"what to repeat next time.\"\n\n## Limitations\n\n- Requires a working local ax installation and reachable local ax database.\n- Only sees sessions, commits, skills, and tool traces that ax has ingested.\n- Session data can be incomplete when an agent provider omits tool output, cost, or reasoning data.\n- It reconstructs workflow, not correctness; still inspect the code and run project checks when making engineering decisions.\n\n## Security & Safety Notes\n\n- Do not upload private transcripts, session logs, prompts, tool outputs, or local database exports.\n- Redact secrets, tokens, customer data, file contents, and private conversation text from summaries.\n- Use read-only ax inspection commands unless the user explicitly asks for a separate maintenance action.\n- Do not run commands that mutate `.ax\u002F`, regenerate indexes, publish reports, or alter repositories as part of reconstruction.\n\n## Related Skills\n\n- `@agenttrace-session-audit` - Use for local agent-session health, cost, latency, and tool-failure audits.\n- `@domain-modeling` - Use when the reconstruction reveals terminology or architectural decisions that should be captured.\n- `@planning-with-files` - Use when the user wants to turn the reconstructed recipe into a new plan with tracked notes.\n","# ax Extract Workflow\n\n## Overview\n\nUse this skill to reconstruct the workflow behind a past coding-agent artifact:\na shipped feature, PR, demo, refactor, report, or other concrete result. It uses\nthe local `ax` graph to connect commits, sessions, turns, skills, and tool traces\ninto a short \"how this got made\" narrative.\n\n`ax` must be installed, available on `PATH`, and able to reach its local database.\nIf ax cannot connect to its DB, report the connection failure and stop instead of\nguessing from memory.\n\n## When to Use This Skill\n\n- Use when the user asks \"how did we build X?\", \"what made X work?\", or \"extract the workflow behind this artifact.\"\n- Use when the anchor is a commit SHA, date, feature name, PR, session, or repo-local artifact.\n- Use when the user wants the sequence of agent skills, prompts, commands, decisions, and checks that led to a result.\n- Do not use for a generic activity summary; use normal session listing instead.\n\n## How It Works\n\n### Step 1: Resolve the Anchor\n\nIdentify the best anchor from the user's request:\n\n- Commit SHA: use it directly.\n- Date or date range: inspect sessions around the date.\n- Topic, feature, or artifact name: search recall for related turns, commits, and skills.\n- \"This repo recently\": list recent sessions for the current repo.\n\n```bash\nax recall \"live ingest dashboard\" --sources=turn,commit,skill --scope=here\nax sessions near abc1234 --json\nax sessions around 2026-06-15 --days=3 --json\nax sessions here --days=14\n```\n\nThese commands are read-only inspection commands.\n\n### Step 2: Pick Relevant Sessions\n\nChoose the few sessions most likely to explain the artifact. Prefer sessions\nthat mention the artifact, touch related files, include relevant commits, or have\nskills and tool calls that match the work.\n\nIf several candidates are plausible, show the user the candidates and ask which\none to inspect.\n\n### Step 3: Inspect the Session Trail\n\nOpen each selected session and look for:\n\n- skills used and their order\n- user steering points and clarified constraints\n- files, tests, and commands that changed the direction of the work\n- subagent or tool traces that produced key evidence\n- verification steps before the result was considered done\n\n```bash\nax sessions show \u003Csession-id> --json\nax sessions show \u003Csession-id> --by-role\nax recall \"specific keyword from the artifact\" --sources=turn,commit --scope=here\n```\n\n### Step 4: Write the Reconstruction\n\nReturn the result inline unless the user asks for a file. Keep it short and\nevidence-grounded:\n\n1. Anchor: the date, commit, feature, or artifact you resolved.\n2. Ordered workflow: 4-8 steps showing the skill or action and what it produced.\n3. Key decisions: the user or agent choices that changed the path.\n4. Verification: tests, reviews, checks, or manual evidence.\n5. Reproducer brief: the compact recipe for doing similar work again.\n\nUse session IDs, commit SHAs, and file paths as citations when available.\n\n## Examples\n\n### Reconstruct a Feature from a Commit\n\n```bash\nax sessions near 8f31c2a --json\nax sessions show \u003Csession-id> --by-role\nax sessions show \u003Csession-id> --json\n```\n\nOutput shape:\n\n```text\nAnchor: 8f31c2a, live ingest dashboard\n\nWorkflow:\n1. Problem framing -> narrowed the failure to stale dashboard polling.\n2. Session recall -> found the earlier ingest-stream design and constraints.\n3. Implementation -> wired the server event bus and browser subscription.\n4. Verification -> ran typecheck and refreshed the dashboard locally.\n\nReproducer brief:\nStart from the failing artifact, find nearby sessions, inspect role-grouped\nskills, then summarize the smallest ordered path from framing to verification.\n```\n\n### Reconstruct Work Around a Date\n\n```bash\nax sessions around 2026-06-15 --days=2 --json\nax recall \"otel receiver\" --sources=turn,commit,skill --scope=here\n```\n\nUse this when the user remembers when the work happened but not the commit.\n\n## Best Practices\n\n- Start from the most concrete anchor available: SHA beats date, date beats vague topic.\n- Treat ax as the source of truth; do not invent missing skills, costs, commands, or decisions.\n- Quote sparingly and only when a user decision or command matters to the reconstruction.\n- Keep private transcript details private; summarize rather than dumping logs.\n- Separate \"what happened\" from \"what to repeat next time.\"\n\n## Limitations\n\n- Requires a working local ax installation and reachable local ax database.\n- Only sees sessions, commits, skills, and tool traces that ax has ingested.\n- Session data can be incomplete when an agent provider omits tool output, cost, or reasoning data.\n- It reconstructs workflow, not correctness; still inspect the code and run project checks when making engineering decisions.\n\n## Security & Safety Notes\n\n- Do not upload private transcripts, session logs, prompts, tool outputs, or local database exports.\n- Redact secrets, tokens, customer data, file contents, and private conversation text from summaries.\n- Use read-only ax inspection commands unless the user explicitly asks for a separate maintenance action.\n- Do not run commands that mutate `.ax\u002F`, regenerate indexes, publish reports, or alter repositories as part of reconstruction.\n\n## Related Skills\n\n- `@agenttrace-session-audit` - Use for local agent-session health, cost, latency, and tool-failure audits.\n- `@domain-modeling` - Use when the reconstruction reveals terminology or architectural decisions that should be captured.\n- `@planning-with-files` - Use when the user wants to turn the reconstructed recipe into a new plan with tracked notes.\n",{"name":5,"risk":24,"tags":25,"tools":30,"author":35,"source":36,"license":37,"category":38,"date_added":39,"description":7,"source_repo":40,"source_type":36,"license_source":41},"safe",[26,27,28,29],"ai-coding","workflow-reconstruction","session-analysis","observability",[31,32,33,34],"claude","cursor","gemini","codex-cli","Necmttn","community","AGPL-3.0-only","development","2026-06-21","Necmttn\u002Fax","https:\u002F\u002Fgithub.com\u002FNecmttn\u002Fax\u002Fblob\u002Fmain\u002FLICENSE","main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Fax-extract-workflow",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":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill ax-extract-workflow",{"tool":55,"command":56},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill ax-extract-workflow",{"tool":58,"command":59},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill ax-extract-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fax-extract-workflow\u002FSKILL.md",true,[],[64,72,79,86,93,100],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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.","MIT","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"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",[],[]]