[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79TCSSW14H5YG10WWWN13KA":3,"skill-same:01M79TCSSW14H5YG10WWWN13KA":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},"01M79TCSSW14H5YG10WWWN13KA","ruby-architect",null,"Architect-level Ruby guidance — application layering beyond fat models and controllers, service and query object boundaries, ActiveRecord usage limits, background job and connection-pool discipline, and the concurrency reality of a Ruby service. Use when designing or reviewing a Ruby (Rails or Rack) 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\u002Fruby-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ruby-architect\ndescription: Architect-level Ruby guidance — application layering beyond fat models and controllers, service and query object boundaries, ActiveRecord usage limits, background job and connection-pool discipline, and the concurrency reality of a Ruby service. Use when designing or reviewing a Ruby (Rails or Rack) backend.\nlicense: MIT\ncompatibility: Ruby 3.2+; Rails 7\u002F8 or Sinatra\u002FRack\nmetadata:\n  crusor-domain: website-architect\n  crusor-path: website-architect\u002Fbackend-development-architect\u002Fruby-architect\n  crusor-origin: original\n  crusor-sources: \"guides.rubyonrails.org; api.rubyonrails.org; shopify.github.io\u002Fruby-style-guide\"\n  crusor-triggers: \"ruby, rails, activerecord, sidekiq, rack, ruby on rails, service objects\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Ruby Architect\n\nRuby's flexibility is the risk: without explicit boundaries, business logic\ndissolves into models, controllers and callbacks.\n\n## When to use\n\n- Rails product development, internal tools, API backends.\n- Existing Ruby codebase whose models have 900 lines.\n\n## When NOT to use\n\n- CPU-bound services or high-concurrency fan-out (Ruby's thread model and GVL\n  make other runtimes cheaper).\n- Edge\u002Fserverless workloads with cold-start constraints.\n\n## Decision 1 — Layering\n\n```\napp\u002Fcontrollers\u002F    params, auth, response codes\n  app\u002Fservices\u002F     use-cases, transactions\n    app\u002Fqueries\u002F    read paths (query objects)\n      app\u002Fmodels\u002F   persistence + small domain behaviour\n```\n\n- A service object takes plain arguments, returns a result, raises typed errors.\n- Controllers never contain business rules; models never call external APIs.\n- Callbacks are for persistence invariants only — anything else is a hidden\n  action that will surprise someone.\n- `concerns\u002F` only for genuinely shared behaviour; it is the most common hiding\n  place for coupling.\n\n## Decision 2 — ActiveRecord discipline\n\n- Scopes for reusable filters; never build queries in views or controllers.\n- Eager-load (`includes`\u002F`preload`) deliberately; N+1 is the default failure.\n- Keep transactions in services, short; no HTTP calls inside them.\n- `find_by` with explicit nil handling; avoid `rescue nil` and `try` chains that\n  hide state.\n- Migrations reversible or explicitly forward-only; no data logic in schema\n  migrations.\n\n## Decision 3 — Concurrency and runtime\n\n- Puma workers × threads sized to the DB pool — the pool is the real limit.\n- Assume the GVL: CPU-heavy work belongs in a job or a separate process.\n- Background jobs (Sidekiq) are idempotent and safe to retry; no job depends on\n  a transient in-memory state.\n- Timeouts: DB statement timeout, HTTP client timeouts, job timeout.\n- Memory bloat: monitor RSS; long-running processes need restart policies.\n\n## Decision 4 — Testing and quality\n\n- Request specs for boundaries, model\u002Funit specs for rules; avoid testing Rails\n  itself.\n- Factories produce the minimum valid object; no shared mutable global state.\n- RuboCop for style, `brakeman` for security, `bundler-audit` for dependencies,\n  all in CI.\n\n## Failure modes at scale\n\n- N+1 queries discovered in production on the busiest page.\n- A callback that sends email inside a transaction.\n- Job retries creating duplicate side effects.\n- Threads > DB pool → connection timeouts under load.\n- A 1,500-line model with 40 public methods used nowhere else.\n\n## Verification receipts\n\n1. Query count per endpoint (no N+1) in request specs.\n2. Transaction duration on the busiest write path.\n3. Puma threads vs pool size documented and load-tested.\n4. Job idempotency test: run twice, one effect.\n5. Brakeman + bundler-audit clean in CI.\n","# Ruby Architect\n\nRuby's flexibility is the risk: without explicit boundaries, business logic\ndissolves into models, controllers and callbacks.\n\n## When to use\n\n- Rails product development, internal tools, API backends.\n- Existing Ruby codebase whose models have 900 lines.\n\n## When NOT to use\n\n- CPU-bound services or high-concurrency fan-out (Ruby's thread model and GVL\n  make other runtimes cheaper).\n- Edge\u002Fserverless workloads with cold-start constraints.\n\n## Decision 1 — Layering\n\n```\napp\u002Fcontrollers\u002F    params, auth, response codes\n  app\u002Fservices\u002F     use-cases, transactions\n    app\u002Fqueries\u002F    read paths (query objects)\n      app\u002Fmodels\u002F   persistence + small domain behaviour\n```\n\n- A service object takes plain arguments, returns a result, raises typed errors.\n- Controllers never contain business rules; models never call external APIs.\n- Callbacks are for persistence invariants only — anything else is a hidden\n  action that will surprise someone.\n- `concerns\u002F` only for genuinely shared behaviour; it is the most common hiding\n  place for coupling.\n\n## Decision 2 — ActiveRecord discipline\n\n- Scopes for reusable filters; never build queries in views or controllers.\n- Eager-load (`includes`\u002F`preload`) deliberately; N+1 is the default failure.\n- Keep transactions in services, short; no HTTP calls inside them.\n- `find_by` with explicit nil handling; avoid `rescue nil` and `try` chains that\n  hide state.\n- Migrations reversible or explicitly forward-only; no data logic in schema\n  migrations.\n\n## Decision 3 — Concurrency and runtime\n\n- Puma workers × threads sized to the DB pool — the pool is the real limit.\n- Assume the GVL: CPU-heavy work belongs in a job or a separate process.\n- Background jobs (Sidekiq) are idempotent and safe to retry; no job depends on\n  a transient in-memory state.\n- Timeouts: DB statement timeout, HTTP client timeouts, job timeout.\n- Memory bloat: monitor RSS; long-running processes need restart policies.\n\n## Decision 4 — Testing and quality\n\n- Request specs for boundaries, model\u002Funit specs for rules; avoid testing Rails\n  itself.\n- Factories produce the minimum valid object; no shared mutable global state.\n- RuboCop for style, `brakeman` for security, `bundler-audit` for dependencies,\n  all in CI.\n\n## Failure modes at scale\n\n- N+1 queries discovered in production on the busiest page.\n- A callback that sends email inside a transaction.\n- Job retries creating duplicate side effects.\n- Threads > DB pool → connection timeouts under load.\n- A 1,500-line model with 40 public methods used nowhere else.\n\n## Verification receipts\n\n1. Query count per endpoint (no N+1) in request specs.\n2. Transaction duration on the busiest write path.\n3. Puma threads vs pool size documented and load-tested.\n4. Job idempotency test: run twice, one effect.\n5. Brakeman + bundler-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\u002Fruby-architect","website-architect","original","guides.rubyonrails.org; api.rubyonrails.org; shopify.github.io\u002Fruby-style-guide","ruby, rails, activerecord, sidekiq, rack, ruby on rails, service objects","2026-10-30","Ruby 3.2+; Rails 7\u002F8 or Sinatra\u002FRack","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fwebsite-architect\u002Fbackend-development-architect\u002Fruby-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 ruby-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill ruby-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill ruby-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fbackend-development-architect\u002Fruby-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",[],[]]