[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DRCSF60PPMS9W80W10T8W0":3,"skill-same:01M7DRCSF60PPMS9W80W10T8W0":66},{"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":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M7DRCSF60PPMS9W80W10T8W0","tree-ring-memory",null,"Use Tree Ring Memory for local-first AI-agent memory lifecycle work: recall, evidence, audit, forgetting, and consolidation without transcript dumping.","Hazek-dc\u002FPresensiGuru_FaceNet_EMAR","Hazek-dc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75208960?v=4","01M7DEQV5B4YGS86A81DYH81DR","Hazek","01M7DEQV5XP4TM0C6NTHXCXCHR",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftree-ring-memory\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: tree-ring-memory\ndescription: \"Use Tree Ring Memory for local-first AI-agent memory lifecycle work: recall, evidence, audit, forgetting, and consolidation without transcript dumping.\"\ncategory: development\nrisk: safe\nsource: community\nsource_repo: TerminallyLazy\u002FTree-Ring-Memory\nsource_type: community\ndate_added: \"2026-07-08\"\nauthor: TerminallyLazy\ntags: [agent-memory, local-first, recall, privacy, codex, sqlite, cli]\ntools: [claude, codex, cursor, gemini, antigravity, opencode]\nlicense: \"Apache-2.0\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002FTerminallyLazy\u002FTree-Ring-Memory\u002Fblob\u002Fmain\u002FLICENSE\"\n---\n\n# Tree Ring Memory\n\n## Overview\n\nTree Ring Memory is a framework-agnostic, local-first memory lifecycle layer for\nAI agents. Use this skill when an agent should recall, preserve, audit, or\nforget durable project memory without treating raw conversation transcripts as\nmemory.\n\nThe public runtime is a Rust CLI\u002FTUI with local SQLite\u002FFTS storage, scoped\nrecall, evidence records, audit, deterministic consolidation, maintenance,\nDOX\u002FRevolve source adapters, framework discovery, redaction, and explicit\nforgetting.\n\n## When to Use This Skill\n\n- Use before resuming a project where prior decisions, warnings, preferences,\n  or failed approaches may matter.\n- Use before changing architecture, storage, security, privacy, release, or\n  agent-memory behavior.\n- Use when the user asks to remember, recall, audit, redact, forget, or\n  consolidate agent memory.\n- Use after tests, reviews, incidents, or production behavior validate a lesson\n  future agents should preserve.\n- Use when a project contains `.tree-ring\u002FSKILL.md`, `.tree-ring\u002FCLI.md`, or\n  other Tree Ring bridge files.\n\n## How It Works\n\n### Step 1: Discover Local Guidance\n\nCheck whether the current project already has Tree Ring guidance:\n\n```bash\ntest -f .tree-ring\u002FSKILL.md && sed -n '1,220p' .tree-ring\u002FSKILL.md\ntest -f .tree-ring\u002FCLI.md && sed -n '1,220p' .tree-ring\u002FCLI.md\n```\n\nTreat project-local `.tree-ring` files as more authoritative than generic\nexamples in this skill. If the CLI is installed, inspect the current command\nsurface before assuming flags:\n\n```bash\ntree-ring --help\ntree-ring recall --help\ntree-ring remember --help\ntree-ring evidence --help\ntree-ring audit --help\ntree-ring forget --help\n```\n\nIf Tree Ring is not installed, do not run remote installer commands\nautomatically. Point the user to the project repository or install docs and ask\nwhether they want installation help.\n\n## Step 2: Recall Before Risky Work\n\nUse narrow, project-scoped recall first:\n\n```bash\ntree-ring recall \"release behavior\" --scope project\ntree-ring recall \"sqlite migration\" --scope project\ntree-ring recall \"user preference\" --scope global\n```\n\nUse recalled memory as context, not authority. Verify it against current source\nfiles, tests, docs, issues, pull requests, logs, and runtime state before making\nchanges.\n\n## Step 3: Write Only Durable Memory\n\nWrite concise memory only when it is likely to help future agents:\n\n```bash\ntree-ring remember \"Run project-scoped recall before release changes.\" --event-type lesson --scope project\n```\n\nPrefer specific event types when supported locally:\n\n- `decision`\n- `lesson`\n- `warning`\n- `correction`\n- `user_preference`\n- `tool_result`\n- `summary`\n- `hypothesis`\n\nStore the durable lesson, decision, warning, or follow-up. Do not store the\nfull conversation.\n\n## Step 4: Record Evidence for Evaluated Outcomes\n\nUse evidence records for test runs, incidents, reviewed changes, or other\nevaluated outcomes:\n\n```bash\ntree-ring evidence \\\n  --outcome observed \\\n  --summary \"Installer smoke test passed in an isolated HOME.\" \\\n  --evidence-ref \"ci\u002Finstall-smoke\u002F2026-07-08\"\n```\n\nOutcome guidance:\n\n- `promoted`: durable truth backed by strong evidence\n- `rejected`: failed or rolled-back approach worth keeping visible\n- `deferred`: unresolved idea or future option\n- `observed`: normal evaluated result\n\nDo not promote weak, stale, or unreviewed claims to durable truth.\n\n## Step 5: Use Source Adapters Carefully\n\nWhen a repo has structured source records, run dry runs first:\n\n```bash\ntree-ring dox sync --source-root . --dry-run\ntree-ring revolve sync --source-root revolve --dry-run\ntree-ring integrations scan --source-root .\n```\n\nOnly write adapter summaries when they are concise, source-linked, useful, and\nprivacy-safe. Imported memory does not replace the underlying `AGENTS.md`,\nRevolve record, test, pull request, issue, or documentation.\n\n## Ring Selection\n\nUse the smallest durable ring that fits:\n\n- `cambium`: active or recent task context\n- `outer`: recent decisions and task lessons\n- `inner`: older compressed project knowledge\n- `heartwood`: durable high-confidence truths\n- `scar`: failures, regressions, rejected approaches, warnings\n- `seed`: unresolved ideas, hypotheses, follow-ups\n\nPrefer `outer` or `seed` unless the user confirms durability or the evidence is\nstrong.\n\n## Best Practices\n\n- Recall before risky or repeat work.\n- Keep project memory project-scoped unless it is a durable cross-project user\n  preference.\n- Attach source references such as file paths, issue ids, PR ids, evaluation\n  runs, or docs paths.\n- Re-check current source files and runtime state before acting on recalled\n  memory.\n- Ask at closeout what future agents should remember, avoid, or revisit.\n- Use redaction, deletion, or supersession when memory is wrong, stale,\n  sensitive, or replaced by a newer decision.\n\n## Security & Safety Notes\n\n- Never use Tree Ring Memory as a hidden recorder.\n- Do not store secrets, credentials, tokens, private keys, recovery codes, raw\n  chain-of-thought, or temporary scratchpad content.\n- Do not store sensitive personal data unless the user explicitly asks and the\n  retention boundary is safe.\n- Do not store copyrighted source text beyond short allowed excerpts.\n- Do not run installer, network, destructive, or mutation commands without\n  explicit user approval and a clear target environment.\n- Treat all examples as commands to adapt after checking local `--help`, not as\n  guaranteed command surfaces.\n\n## Limitations\n\n- Tree Ring Memory is not a replacement for source control, issue trackers,\n  documentation, tests, logs, or live runtime verification.\n- Recalled memory can be stale or wrong. Always verify important claims against\n  the current project before using them to make changes.\n- The CLI surface can change across releases. Prefer local `.tree-ring`\n  guidance and `tree-ring --help` over copied command examples.\n- It should not be used for secret storage, comprehensive transcript archives,\n  compliance retention, or unreviewed collection of sensitive personal data.\n- Cross-agent interoperability depends on each tool's ability to call the local\n  CLI or read project-local guidance files.\n\n## Common Pitfalls\n\n- **Problem:** Recalled memory conflicts with current source.\n  **Solution:** Treat source files, tests, docs, and runtime evidence as\n  authoritative; supersede or forget stale memory.\n\n- **Problem:** Memory starts becoming transcript storage.\n  **Solution:** Store only durable decisions, warnings, preferences, outcomes,\n  and follow-ups.\n\n- **Problem:** A lesson is useful but contains sensitive detail.\n  **Solution:** Store a redacted summary or do not store it.\n\n## Related Skills\n\n- `@agent-memory-systems` - Use for broad agent-memory architecture choices.\n- `@agent-memory` - Use for the listed hybrid memory MCP system.\n- `@planning-with-files` - Use when simple persistent files are enough.\n\n## Additional Resources\n\n- Tree Ring Memory repository: \u003Chttps:\u002F\u002Fgithub.com\u002FTerminallyLazy\u002FTree-Ring-Memory>\n- Codex plugin wrapper: \u003Chttps:\u002F\u002Fgithub.com\u002FTerminallyLazy\u002Ftree-ring-memory-codex-plugin>\n","# Tree Ring Memory\n\n## Overview\n\nTree Ring Memory is a framework-agnostic, local-first memory lifecycle layer for\nAI agents. Use this skill when an agent should recall, preserve, audit, or\nforget durable project memory without treating raw conversation transcripts as\nmemory.\n\nThe public runtime is a Rust CLI\u002FTUI with local SQLite\u002FFTS storage, scoped\nrecall, evidence records, audit, deterministic consolidation, maintenance,\nDOX\u002FRevolve source adapters, framework discovery, redaction, and explicit\nforgetting.\n\n## When to Use This Skill\n\n- Use before resuming a project where prior decisions, warnings, preferences,\n  or failed approaches may matter.\n- Use before changing architecture, storage, security, privacy, release, or\n  agent-memory behavior.\n- Use when the user asks to remember, recall, audit, redact, forget, or\n  consolidate agent memory.\n- Use after tests, reviews, incidents, or production behavior validate a lesson\n  future agents should preserve.\n- Use when a project contains `.tree-ring\u002FSKILL.md`, `.tree-ring\u002FCLI.md`, or\n  other Tree Ring bridge files.\n\n## How It Works\n\n### Step 1: Discover Local Guidance\n\nCheck whether the current project already has Tree Ring guidance:\n\n```bash\ntest -f .tree-ring\u002FSKILL.md && sed -n '1,220p' .tree-ring\u002FSKILL.md\ntest -f .tree-ring\u002FCLI.md && sed -n '1,220p' .tree-ring\u002FCLI.md\n```\n\nTreat project-local `.tree-ring` files as more authoritative than generic\nexamples in this skill. If the CLI is installed, inspect the current command\nsurface before assuming flags:\n\n```bash\ntree-ring --help\ntree-ring recall --help\ntree-ring remember --help\ntree-ring evidence --help\ntree-ring audit --help\ntree-ring forget --help\n```\n\nIf Tree Ring is not installed, do not run remote installer commands\nautomatically. Point the user to the project repository or install docs and ask\nwhether they want installation help.\n\n## Step 2: Recall Before Risky Work\n\nUse narrow, project-scoped recall first:\n\n```bash\ntree-ring recall \"release behavior\" --scope project\ntree-ring recall \"sqlite migration\" --scope project\ntree-ring recall \"user preference\" --scope global\n```\n\nUse recalled memory as context, not authority. Verify it against current source\nfiles, tests, docs, issues, pull requests, logs, and runtime state before making\nchanges.\n\n## Step 3: Write Only Durable Memory\n\nWrite concise memory only when it is likely to help future agents:\n\n```bash\ntree-ring remember \"Run project-scoped recall before release changes.\" --event-type lesson --scope project\n```\n\nPrefer specific event types when supported locally:\n\n- `decision`\n- `lesson`\n- `warning`\n- `correction`\n- `user_preference`\n- `tool_result`\n- `summary`\n- `hypothesis`\n\nStore the durable lesson, decision, warning, or follow-up. Do not store the\nfull conversation.\n\n## Step 4: Record Evidence for Evaluated Outcomes\n\nUse evidence records for test runs, incidents, reviewed changes, or other\nevaluated outcomes:\n\n```bash\ntree-ring evidence \\\n  --outcome observed \\\n  --summary \"Installer smoke test passed in an isolated HOME.\" \\\n  --evidence-ref \"ci\u002Finstall-smoke\u002F2026-07-08\"\n```\n\nOutcome guidance:\n\n- `promoted`: durable truth backed by strong evidence\n- `rejected`: failed or rolled-back approach worth keeping visible\n- `deferred`: unresolved idea or future option\n- `observed`: normal evaluated result\n\nDo not promote weak, stale, or unreviewed claims to durable truth.\n\n## Step 5: Use Source Adapters Carefully\n\nWhen a repo has structured source records, run dry runs first:\n\n```bash\ntree-ring dox sync --source-root . --dry-run\ntree-ring revolve sync --source-root revolve --dry-run\ntree-ring integrations scan --source-root .\n```\n\nOnly write adapter summaries when they are concise, source-linked, useful, and\nprivacy-safe. Imported memory does not replace the underlying `AGENTS.md`,\nRevolve record, test, pull request, issue, or documentation.\n\n## Ring Selection\n\nUse the smallest durable ring that fits:\n\n- `cambium`: active or recent task context\n- `outer`: recent decisions and task lessons\n- `inner`: older compressed project knowledge\n- `heartwood`: durable high-confidence truths\n- `scar`: failures, regressions, rejected approaches, warnings\n- `seed`: unresolved ideas, hypotheses, follow-ups\n\nPrefer `outer` or `seed` unless the user confirms durability or the evidence is\nstrong.\n\n## Best Practices\n\n- Recall before risky or repeat work.\n- Keep project memory project-scoped unless it is a durable cross-project user\n  preference.\n- Attach source references such as file paths, issue ids, PR ids, evaluation\n  runs, or docs paths.\n- Re-check current source files and runtime state before acting on recalled\n  memory.\n- Ask at closeout what future agents should remember, avoid, or revisit.\n- Use redaction, deletion, or supersession when memory is wrong, stale,\n  sensitive, or replaced by a newer decision.\n\n## Security & Safety Notes\n\n- Never use Tree Ring Memory as a hidden recorder.\n- Do not store secrets, credentials, tokens, private keys, recovery codes, raw\n  chain-of-thought, or temporary scratchpad content.\n- Do not store sensitive personal data unless the user explicitly asks and the\n  retention boundary is safe.\n- Do not store copyrighted source text beyond short allowed excerpts.\n- Do not run installer, network, destructive, or mutation commands without\n  explicit user approval and a clear target environment.\n- Treat all examples as commands to adapt after checking local `--help`, not as\n  guaranteed command surfaces.\n\n## Limitations\n\n- Tree Ring Memory is not a replacement for source control, issue trackers,\n  documentation, tests, logs, or live runtime verification.\n- Recalled memory can be stale or wrong. Always verify important claims against\n  the current project before using them to make changes.\n- The CLI surface can change across releases. Prefer local `.tree-ring`\n  guidance and `tree-ring --help` over copied command examples.\n- It should not be used for secret storage, comprehensive transcript archives,\n  compliance retention, or unreviewed collection of sensitive personal data.\n- Cross-agent interoperability depends on each tool's ability to call the local\n  CLI or read project-local guidance files.\n\n## Common Pitfalls\n\n- **Problem:** Recalled memory conflicts with current source.\n  **Solution:** Treat source files, tests, docs, and runtime evidence as\n  authoritative; supersede or forget stale memory.\n\n- **Problem:** Memory starts becoming transcript storage.\n  **Solution:** Store only durable decisions, warnings, preferences, outcomes,\n  and follow-ups.\n\n- **Problem:** A lesson is useful but contains sensitive detail.\n  **Solution:** Store a redacted summary or do not store it.\n\n## Related Skills\n\n- `@agent-memory-systems` - Use for broad agent-memory architecture choices.\n- `@agent-memory` - Use for the listed hybrid memory MCP system.\n- `@planning-with-files` - Use when simple persistent files are enough.\n\n## Additional Resources\n\n- Tree Ring Memory repository: \u003Chttps:\u002F\u002Fgithub.com\u002FTerminallyLazy\u002FTree-Ring-Memory>\n- Codex plugin wrapper: \u003Chttps:\u002F\u002Fgithub.com\u002FTerminallyLazy\u002Ftree-ring-memory-codex-plugin>\n",{"name":5,"risk":24,"tags":25,"tools":33,"author":39,"source":40,"license":15,"category":41,"date_added":42,"description":7,"source_repo":43,"source_type":40,"license_source":44},"safe",[26,27,28,29,30,31,32],"agent-memory","local-first","recall","privacy","codex","sqlite","cli",[34,30,35,36,37,38],"claude","cursor","gemini","antigravity","opencode","TerminallyLazy","community","development","2026-07-08","TerminallyLazy\u002FTree-Ring-Memory","https:\u002F\u002Fgithub.com\u002FTerminallyLazy\u002FTree-Ring-Memory\u002Fblob\u002Fmain\u002FLICENSE","main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Ftree-ring-memory",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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill tree-ring-memory",{"tool":58,"command":59},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill tree-ring-memory",{"tool":61,"command":62},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill tree-ring-memory","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftree-ring-memory\u002FSKILL.md",true,[],[67,75,82,89,96,103],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"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",[],[]]