[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79TBKZKFN76TYQ1QM4RCPPF":3,"skill-same:01M79TBKZKFN76TYQ1QM4RCPPF":53},{"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":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M79TBKZKFN76TYQ1QM4RCPPF","php-architect",null,"Architect-level PHP guidance — framework and layering choices, request lifecycle and shared-nothing deployment, autoloading and dependency injection, database and session boundaries, and the operational reality of PHP-FPM. Use when designing or reviewing a PHP backend.","SriAkhilSJ\u002FPulseAIRepo","SriAkhilSJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206201543?v=4","01M79RWFD1Q09B89SXTTKKJY6Z","Sri Akhil SJ","01M79RWFE26NPG0BZ1FRNX376H",0,"MIT","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fbackend-development-architect\u002Fphp-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: php-architect\ndescription: Architect-level PHP guidance — framework and layering choices, request lifecycle and shared-nothing deployment, autoloading and dependency injection, database and session boundaries, and the operational reality of PHP-FPM. Use when designing or reviewing a PHP backend.\nlicense: MIT\ncompatibility: PHP 8.2+; Laravel \u002F Symfony \u002F plain PSR-15\nmetadata:\n  crusor-domain: website-architect\n  crusor-path: website-architect\u002Fbackend-development-architect\u002Fphp-architect\n  crusor-origin: original\n  crusor-sources: \"php.net\u002Fmanual; laravel.com\u002Fdocs; symfony.com\u002Fdoc\u002Fcurrent; php-fig.org\u002Fpsr\"\n  crusor-triggers: \"php, laravel, symfony, php-fpm, composer, psr, eloquent, blade\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# PHP Architect\n\nPHP's defining property is **shared-nothing**: each request starts clean. That is\na strength — until someone reintroduces hidden global state.\n\n## When to use\n\n- Content platforms, e-commerce, internal apps with a PHP team.\n- Laravel\u002FSymfony projects needing boundaries beyond \"everything in controllers\".\n- Migrating legacy PHP into a maintained structure.\n\n## When NOT to use\n\n- Long-running, stateful services (websockets, workers) — possible, but other\n  runtimes fit better.\n\n## Decision 1 — Structure\n\n```\npublic\u002Findex.php     front controller, nothing else\n  src\u002FHttp\u002F          controllers, requests\u002Fvalidation\n    src\u002FDomain\u002F      entities, value objects, rules\n      src\u002FApplication\u002F services, use-cases\n        src\u002FInfrastructure\u002F repositories, external clients\n```\n\n- PSR-4 autoloading; one class per file; `composer` owns the autoloader.\n- Framework code stays in `Http`\u002F`Infrastructure`; the domain has no framework\n  imports.\n- Dependency injection via the container, constructor injection only; no service\n  locators inside domain code.\n\n## Decision 2 — Request lifecycle\n\n| Concern | Rule |\n|---|---|\n| validation | at the edge (FormRequest\u002FValidator), typed DTO inward |\n| auth | middleware\u002Fguard; authorization policies per resource |\n| sessions | server-side store, regenerated on login |\n| output | escaped by default (Blade\u002FTwig); raw output requires a sanitiser |\n| errors | one handler → JSON envelope, never a stack trace |\n\n- Shared-nothing means no static caches surviving a request — use the cache\n  backend, not a static property.\n- Config from environment, validated at boot; `env()` outside config files is a\n  bug.\n\n## Decision 3 — Data access\n\n- Eloquent\u002FDoctrine are fine in `Infrastructure`; the domain sees repository\n  interfaces.\n- Eager-load relations (`with()`), otherwise N+1 is guaranteed on list pages.\n- Migrations versioned and reversible; no manual DDL in production.\n- Transactions in services; no email\u002FHTTP calls inside a transaction.\n\n## Decision 4 — Runtime and operations\n\n- PHP-FPM pool sized to CPU and DB connections; `pm.max_children` is the real\n  concurrency limit.\n- Opcache enabled in production; `preload` only after measuring.\n- Queues (Horizon\u002FWorker) for anything slow; jobs idempotent.\n- Deploy: build artefacts, `composer install --no-dev --optimize-autoloader`,\n  cache warm-up, then release — no `composer update` on the production box.\n\n## Failure modes at scale\n\n- Business logic in Blade templates.\n- `env()` called in application code (breaks once config is cached).\n- N+1 on the product listing page.\n- Unbounded FPM children exhausting DB connections.\n- A deploy that runs migrations and code changes at the same instant, with no\n  rollback path.\n\n## Verification receipts\n\n1. Query count on the busiest list page (eager loading proven).\n2. Config cache + opcache verified in production.\n3. FPM children vs DB max_connections documented.\n4. Queue job idempotency test.\n5. Static analysis (PHPStan\u002FPsalm) and `composer audit` clean in CI.\n","# PHP Architect\n\nPHP's defining property is **shared-nothing**: each request starts clean. That is\na strength — until someone reintroduces hidden global state.\n\n## When to use\n\n- Content platforms, e-commerce, internal apps with a PHP team.\n- Laravel\u002FSymfony projects needing boundaries beyond \"everything in controllers\".\n- Migrating legacy PHP into a maintained structure.\n\n## When NOT to use\n\n- Long-running, stateful services (websockets, workers) — possible, but other\n  runtimes fit better.\n\n## Decision 1 — Structure\n\n```\npublic\u002Findex.php     front controller, nothing else\n  src\u002FHttp\u002F          controllers, requests\u002Fvalidation\n    src\u002FDomain\u002F      entities, value objects, rules\n      src\u002FApplication\u002F services, use-cases\n        src\u002FInfrastructure\u002F repositories, external clients\n```\n\n- PSR-4 autoloading; one class per file; `composer` owns the autoloader.\n- Framework code stays in `Http`\u002F`Infrastructure`; the domain has no framework\n  imports.\n- Dependency injection via the container, constructor injection only; no service\n  locators inside domain code.\n\n## Decision 2 — Request lifecycle\n\n| Concern | Rule |\n|---|---|\n| validation | at the edge (FormRequest\u002FValidator), typed DTO inward |\n| auth | middleware\u002Fguard; authorization policies per resource |\n| sessions | server-side store, regenerated on login |\n| output | escaped by default (Blade\u002FTwig); raw output requires a sanitiser |\n| errors | one handler → JSON envelope, never a stack trace |\n\n- Shared-nothing means no static caches surviving a request — use the cache\n  backend, not a static property.\n- Config from environment, validated at boot; `env()` outside config files is a\n  bug.\n\n## Decision 3 — Data access\n\n- Eloquent\u002FDoctrine are fine in `Infrastructure`; the domain sees repository\n  interfaces.\n- Eager-load relations (`with()`), otherwise N+1 is guaranteed on list pages.\n- Migrations versioned and reversible; no manual DDL in production.\n- Transactions in services; no email\u002FHTTP calls inside a transaction.\n\n## Decision 4 — Runtime and operations\n\n- PHP-FPM pool sized to CPU and DB connections; `pm.max_children` is the real\n  concurrency limit.\n- Opcache enabled in production; `preload` only after measuring.\n- Queues (Horizon\u002FWorker) for anything slow; jobs idempotent.\n- Deploy: build artefacts, `composer install --no-dev --optimize-autoloader`,\n  cache warm-up, then release — no `composer update` on the production box.\n\n## Failure modes at scale\n\n- Business logic in Blade templates.\n- `env()` called in application code (breaks once config is cached).\n- N+1 on the product listing page.\n- Unbounded FPM children exhausting DB connections.\n- A deploy that runs migrations and code changes at the same instant, with no\n  rollback path.\n\n## Verification receipts\n\n1. Query count on the busiest list page (eager loading proven).\n2. Config cache + opcache verified in production.\n3. FPM children vs DB max_connections documented.\n4. Queue job idempotency test.\n5. Static analysis (PHPStan\u002FPsalm) and `composer audit` clean in CI.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":31},{"crusor-path":25,"crusor-domain":26,"crusor-origin":27,"crusor-sources":28,"crusor-triggers":29,"crusor-verified-on":30},"website-architect\u002Fbackend-development-architect\u002Fphp-architect","website-architect","original","php.net\u002Fmanual; laravel.com\u002Fdocs; symfony.com\u002Fdoc\u002Fcurrent; php-fig.org\u002Fpsr","php, laravel, symfony, php-fpm, composer, psr, eloquent, blade","2026-10-30","PHP 8.2+; Laravel \u002F Symfony \u002F plain PSR-15","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fwebsite-architect\u002Fbackend-development-architect\u002Fphp-architect","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ","Studying in CMR institute of Technology\r\n2024 - 2028","2026-11-13 21:02:23",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add SriAkhilSJ\u002FPulseAIRepo --skill php-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill php-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill php-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fbackend-development-architect\u002Fphp-architect\u002FSKILL.md",true,[],[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79TTAJNACCNXCEN3649CMMD","interaction-patterns-architect","Architect-level interaction design in code — choosing established patterns over invented ones, feedback and latency behaviour, destructive-action safeguards, navigation and overlay conventions, and the state model behind every interactive surface. Use when a screen has to behave, not just look.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Finteraction-patterns-architect\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79TT2ESKB1TKZBYY9KYJHV9","design-system-ops-architect","Architect-level operation of a design system in code — token pipelines and versioning, component API and variant policy, the catalogue as the contract, adoption metrics, and the governance that stops a system from forking into three. Use when a component library must survive several teams.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-system-ops-architect\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79TSV0PWGNK3PRX9P4JDR9N","design-handoff-architect","Architect-level design handoff — what must be specified before implementation starts, tokens over raw values, responsive and content-limit contracts, state matrices, and the review loop that catches drift between design and code. Use when a design is about to become code.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-handoff-architect\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":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79TSJS9BFXNP696FMJ9GKDA","content-microcopy-architect","Architect-level UI content — where strings live, voice and terminology consistency, error and empty-state copy as part of the interface, translation-ready authoring, and the content model a product needs before it multiplies screens. Use when the words in the interface matter as much as the pixels.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fcontent-microcopy-architect\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":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79TSCNBST3N1M68V1KPH9HQ","ui-ux-implementation-architect","Architect-level direction for turning a design into working UI — the handoff contract, component ownership versus screen-level layout, interaction and state conventions, design QA gates, and the review habits that keep an implementation faithful without frozen pixels. Use before any specific UI implementation skill.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\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":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79TS4N6A4D2QQ433VXS5D0R","test-strategy-architect","Architect-level test strategy — allocating assertions across unit, integration, contract and end-to-end layers, designing for testability through dependency boundaries, fixture and data strategy, and the flake and coverage policies that keep a suite trustworthy. Use when defining how a codebase is tested.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Ftest-strategy-architect\u002FSKILL.md",[],[]]