[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A34QC0R6974BYHT3QJ87CZ":3,"skill-same:01M7A34QC0R6974BYHT3QJ87CZ":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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M7A34QC0R6974BYHT3QJ87CZ","aws-sst-development",null,"SST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework. Use when writing or editing sst.config.ts, building infra\u002F modules (sst.aws.Function\u002FBucket\u002FDynamo\u002FCron\u002FService\u002FRouter, sst.Secret, sst.Linkable, raw aws.* Pulumi resources), wiring resource links,...","MHassan0000\u002FSkills","MHassan0000","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F224296448?v=4","01M7A14DTC1EZCRN04582533RD","Muhammad Hassan Yousaf","01M7A14DV10KTW8NHQTJPD08X0",1,"MIT","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Faws-sst-development\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: aws-sst-development\ndescription: SST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework. Use when writing or editing sst.config.ts, building infra\u002F modules (sst.aws.Function\u002FBucket\u002FDynamo\u002FCron\u002FService\u002FRouter, sst.Secret, sst.Linkable, raw aws.* Pulumi resources), wiring resource links,...\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fzxkane\u002Faws-skills\u002Ftree\u002Fmain\u002Fplugins\u002Faws-iac\u002Fskills\u002Faws-sst-development\nsource_repo: zxkane\u002Faws-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fzxkane\u002Faws-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# SST v4 for AWS\n## When to Use\n\nUse this skill when you need sST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework. Use when writing or editing sst.config.ts, building infra\u002F modules (sst.aws.Function\u002FBucket\u002FDynamo\u002FCron\u002FService\u002FRouter, sst.Secret, sst.Linkable, raw aws.* Pulumi resources), wiring resource links,...\n\n\nSST v4 (the \"Ion\" engine) is a Pulumi-backed IaC framework: you describe AWS\nresources in TypeScript and SST\u002FPulumi reconciles them into your account. It\ngives you high-level `sst.aws.*` components (Function, Bucket, Dynamo, Cron,\nService, …) that expand into many underlying resources, plus an escape hatch to\n*any* raw Pulumi `aws.*` resource for the long tail. This skill encodes a\nproduction-proven way to author, link, test, deploy, and troubleshoot SST\nstacks on AWS — distilled from real multi-stack projects that have paid for\neach lesson with a prod incident.\n\n**SST and Pulumi are third-party — verify current syntax with Context7**\n(`resolve-library-id` → `query-docs` for `sst` or `pulumi-aws`) when you're\nunsure about a component's options. Verify AWS-side facts (service limits,\nmodel IDs, IAM action names, region availability) with the AWS docs MCP, never\nfrom memory. The patterns here are the *how*; the docs are the *what*.\n\n## When you're invoked\n\nFigure out which mode you're in and jump to the right reference:\n\n| Situation | Go to |\n|-----------|-------|\n| New project, or adding a resource\u002Fmodule to an existing SST app | **Author** → `references\u002Fauthoring.md` |\n| Wiring one module's output into another (links, SSM, IAM scope) | **Author** → `references\u002Fauthoring.md` § Sharing |\n| Writing tests for infra so changes don't silently break | **Test** → `references\u002Ftesting.md` |\n| Running a deploy, or a deploy just failed | **Deploy\u002FOperate** → `references\u002Fdeploy-and-troubleshoot.md` |\n| Migrating a resource between Pulumi types, renaming a physical name | **Deploy\u002FOperate** → `references\u002Fdeploy-and-troubleshoot.md` § Migrations |\n\nAlways read the relevant reference before editing — they carry the *why* behind\neach rule, which matters more than the rule itself.\n\n## Orientation: read the repo before you touch it\n\nSST projects are conventional but not identical. Before editing, build a quick\nmap so your change matches the house style instead of fighting it:\n\n1. **`sst.config.ts`** — the app name, `home`, providers\u002Fregion, `defaultTags`,\n   any global `$transform` (Node runtime pin, bundle fixups), and the order in\n   which `run()` imports `infra\u002F` modules. The import order *is* the dependency\n   order; respect it.\n2. **`infra\u002F`** — one file per domain (storage, functions, api, observability…).\n   This is where resources are declared. Check for an `infra\u002FCLAUDE.md` — these\n   projects keep IaC-specific rules there, and it's the single most valuable\n   file to read first.\n3. **`infra\u002Ftests\u002F`** — source-level Vitest assertions that pin resource\n   invariants. If they exist, your change must keep them green and probably\n   needs a new assertion.\n4. **`package.json` \u002F `.nvmrc`** — package manager (npm vs pnpm), Node version,\n   and the `sst`\u002F`pulumi` versions actually installed.\n\nRun `npx sst version` to confirm you're on v4\u002FIon (the `$config` + `.sst\u002Fplatform\u002F`\nsignature). v2\u002Fv3 (\"SST Classic\", CDK-based) is a different framework — these\npatterns don't apply there.\n\n## The conventions, and which are universal vs tunable\n\nThe projects this skill is built from share a deliberate house style. Some of it\nis **universal** (true for any SST v4 + AWS project — apply it everywhere); some\nis **project-specific** (a sensible default these projects chose — adopt it for\nconsistency, but recognize a project may differ).\n\n**Universal — these principles hold for any SST v4 + AWS project:**\n\n- **Control the Node runtime deliberately, in one place.** Don't leave it to\n  whatever the installed SST happens to default to. The idiom is a single global\n  `$transform(sst.aws.Function, (args) => { args.runtime ??= \"nodejs24.x\" })` in\n  `run()` — `??=` is correct here (the transform runs before the component\n  applies its own default, so it fills in only when the user didn't set one).\n  Recent SST already defaults to a current Node runtime, so check the installed\n  default first (Context7); the transform is then version-independence insurance\n  so a future SST downgrade can't silently move your fleet. See\n  `references\u002Fauthoring.md`.\n- **Never interpolate a Pulumi `Output\u003CT>` into a plain JS template literal.**\n  Use `$interpolate` (or `pulumi.interpolate`). A bare top-level\n  `` `${bucket.arn}\u002F*` `` stringifies the `Output` to a `[Output\u003CT>]` placeholder\n  and produces a broken ARN that only fails at deploy time (it type-checks and\n  `sst dev` runs fine). The fix is `$interpolate`​`` `${bucket.arn}\u002F*` ``. This\n  has caused prod deploy outages. See `references\u002Fauthoring.md` § Outputs.\n- **Migrating a resource between Pulumi *types* should default to two PRs** —\n  Pulumi creates-before-destroys, so for a uniqueness-constrained AWS name\n  (bucket, IAM role, gateway) the old resource still owns it and the create\n  fails with `ConflictException`. Two sequential deploys (teardown, then\n  recreate) is the conservative default; `aliases:` \u002F `pulumi import` \u002F state\n  surgery can bridge identity in some cases but only with a reviewed plan. See\n  `references\u002Fdeploy-and-troubleshoot.md` § Migrations.\n- **Prefer typed `sst.aws.*` \u002F `aws.*` resources over the\n  `aws.cloudcontrol.Resource` escape hatch.** CloudControl outputs are\n  stringly-typed and `oneOf` fields don't patch cleanly. Use it only when no\n  typed resource exists yet, and migrate off it when one ships.\n\n**Project-specific defaults — adopt for consistency, but confirm per repo:**\n\n- **Region `ap-northeast-1`**, `home: \"aws\"`, and `defaultTags` carrying\n  `Project` \u002F `Stage` \u002F `ManagedBy: \"sst\"`.\n- **Stage-gated lifecycle**: `removal: stage === \"prod\" ? \"retain\" : \"remove\"`\n  and `protect: stage === \"prod\"` so prod resources survive a stack tear-down\n  and non-prod previews clean up.\n- **SSM Parameter Store as the out-of-graph contract** under a\n  `\u002F{app}\u002F{stage}\u002F{domain}\u002F...` prefix — for consumers that aren't in the\n  Pulumi graph (CI scripts, sibling apps, operators). For *same-app* Lambdas,\n  prefer SST `link:` (it wires a real dependency edge and grants IAM); don't\n  route same-app sharing through SSM. See `references\u002Fauthoring.md` § Sharing.\n- **Lazy `await import(\".\u002Finfra\u002F\u003Cmodule>\")` inside `run()`** so `sst dev`\n  hot-reload stays light. (For testing, a module export still runs its top-level\n  `new sst.aws.*` unless it's wrapped in a factory function — see\n  `references\u002Ftesting.md` for how to test infra.)\n- **Source-level Vitest tests** on every infra module — a lightweight,\n  house-style regression net asserting on the *source text* (resource names,\n  index shapes, IAM scopes). It's a deliberate choice, not an SST limit: Pulumi\n  *does* support runtime mocks (`@pulumi\u002Fpulumi\u002Fruntime`) for behavioral graph\n  tests when a module has real logic. Source assertions don't replace a\n  preview-deploy + smoke test. See `references\u002Ftesting.md`.\n- **An observability gate**: every new Lambda\u002Fqueue\u002Fschedule gets an alarm and\n  structured logging before merge. Whether you enforce this depends on the\n  project, but it's cheap insurance. See `references\u002Fdeploy-and-troubleshoot.md`\n  § Observability.\n\nWhen you introduce a convention, say which bucket it's in (\"this is universal\"\nvs \"matching this repo's house style\") so the user can override the\nproject-specific ones deliberately.\n\n## Working rhythm\n\n1. **Orient** (above) — map config, modules, tests, tooling.\n2. **Verify syntax** with Context7 \u002F AWS docs MCP if anything is non-obvious.\n   Don't guess at a component's option name.\n3. **Author** the resource\u002Fmodule following `references\u002Fauthoring.md`. Match the\n   surrounding file's commenting density and naming — these projects comment the\n   *why* heavily, and a terse one-liner in a heavily-annotated file reads as a\n   regression.\n4. **Test** — add or update source-level assertions (`references\u002Ftesting.md`) and\n   run `npx vitest` (or the repo's `test` script). Run `npx sst diff` and\u002For\n   `tsc --noEmit` to catch type and plan errors before deploying.\n5. **Deploy\u002Foperate** per `references\u002Fdeploy-and-troubleshoot.md`. Confirm the\n   target account with `aws sts get-caller-identity` before any `sst deploy`.\n6. **Clean up** any exported state files — they contain account IDs and ARNs and\n   must not linger in `\u002Ftmp` or chat history.\n\n## What good looks like\n\n- The change is the smallest diff that satisfies the requirement, in the right\n  `infra\u002F` module, wired into `run()` in dependency order.\n- Every Lambda gets the right runtime via the global transform (you didn't\n  hand-set `runtime` unless intentionally diverging — e.g. a Python function).\n- Cross-resource references use `link:` (in-graph) and\u002For `$interpolate`-scoped\n  IAM; outputs other tools consume are published to SSM under the stage prefix.\n- New infra has a matching source-level test, and the existing suite stays green.\n- You confirmed AWS-side facts via the docs MCP and SST\u002FPulumi syntax via\n  Context7 rather than relying on recall.\n- Anything irreversible (deploy, `sst remove`, a resource-type migration) was\n  flagged to the user with the account it targets, and migrations were planned\n  as two PRs, not one.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# SST v4 for AWS\n## When to Use\n\nUse this skill when you need sST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework. Use when writing or editing sst.config.ts, building infra\u002F modules (sst.aws.Function\u002FBucket\u002FDynamo\u002FCron\u002FService\u002FRouter, sst.Secret, sst.Linkable, raw aws.* Pulumi resources), wiring resource links,...\n\n\nSST v4 (the \"Ion\" engine) is a Pulumi-backed IaC framework: you describe AWS\nresources in TypeScript and SST\u002FPulumi reconciles them into your account. It\ngives you high-level `sst.aws.*` components (Function, Bucket, Dynamo, Cron,\nService, …) that expand into many underlying resources, plus an escape hatch to\n*any* raw Pulumi `aws.*` resource for the long tail. This skill encodes a\nproduction-proven way to author, link, test, deploy, and troubleshoot SST\nstacks on AWS — distilled from real multi-stack projects that have paid for\neach lesson with a prod incident.\n\n**SST and Pulumi are third-party — verify current syntax with Context7**\n(`resolve-library-id` → `query-docs` for `sst` or `pulumi-aws`) when you're\nunsure about a component's options. Verify AWS-side facts (service limits,\nmodel IDs, IAM action names, region availability) with the AWS docs MCP, never\nfrom memory. The patterns here are the *how*; the docs are the *what*.\n\n## When you're invoked\n\nFigure out which mode you're in and jump to the right reference:\n\n| Situation | Go to |\n|-----------|-------|\n| New project, or adding a resource\u002Fmodule to an existing SST app | **Author** → `references\u002Fauthoring.md` |\n| Wiring one module's output into another (links, SSM, IAM scope) | **Author** → `references\u002Fauthoring.md` § Sharing |\n| Writing tests for infra so changes don't silently break | **Test** → `references\u002Ftesting.md` |\n| Running a deploy, or a deploy just failed | **Deploy\u002FOperate** → `references\u002Fdeploy-and-troubleshoot.md` |\n| Migrating a resource between Pulumi types, renaming a physical name | **Deploy\u002FOperate** → `references\u002Fdeploy-and-troubleshoot.md` § Migrations |\n\nAlways read the relevant reference before editing — they carry the *why* behind\neach rule, which matters more than the rule itself.\n\n## Orientation: read the repo before you touch it\n\nSST projects are conventional but not identical. Before editing, build a quick\nmap so your change matches the house style instead of fighting it:\n\n1. **`sst.config.ts`** — the app name, `home`, providers\u002Fregion, `defaultTags`,\n   any global `$transform` (Node runtime pin, bundle fixups), and the order in\n   which `run()` imports `infra\u002F` modules. The import order *is* the dependency\n   order; respect it.\n2. **`infra\u002F`** — one file per domain (storage, functions, api, observability…).\n   This is where resources are declared. Check for an `infra\u002FCLAUDE.md` — these\n   projects keep IaC-specific rules there, and it's the single most valuable\n   file to read first.\n3. **`infra\u002Ftests\u002F`** — source-level Vitest assertions that pin resource\n   invariants. If they exist, your change must keep them green and probably\n   needs a new assertion.\n4. **`package.json` \u002F `.nvmrc`** — package manager (npm vs pnpm), Node version,\n   and the `sst`\u002F`pulumi` versions actually installed.\n\nRun `npx sst version` to confirm you're on v4\u002FIon (the `$config` + `.sst\u002Fplatform\u002F`\nsignature). v2\u002Fv3 (\"SST Classic\", CDK-based) is a different framework — these\npatterns don't apply there.\n\n## The conventions, and which are universal vs tunable\n\nThe projects this skill is built from share a deliberate house style. Some of it\nis **universal** (true for any SST v4 + AWS project — apply it everywhere); some\nis **project-specific** (a sensible default these projects chose — adopt it for\nconsistency, but recognize a project may differ).\n\n**Universal — these principles hold for any SST v4 + AWS project:**\n\n- **Control the Node runtime deliberately, in one place.** Don't leave it to\n  whatever the installed SST happens to default to. The idiom is a single global\n  `$transform(sst.aws.Function, (args) => { args.runtime ??= \"nodejs24.x\" })` in\n  `run()` — `??=` is correct here (the transform runs before the component\n  applies its own default, so it fills in only when the user didn't set one).\n  Recent SST already defaults to a current Node runtime, so check the installed\n  default first (Context7); the transform is then version-independence insurance\n  so a future SST downgrade can't silently move your fleet. See\n  `references\u002Fauthoring.md`.\n- **Never interpolate a Pulumi `Output\u003CT>` into a plain JS template literal.**\n  Use `$interpolate` (or `pulumi.interpolate`). A bare top-level\n  `` `${bucket.arn}\u002F*` `` stringifies the `Output` to a `[Output\u003CT>]` placeholder\n  and produces a broken ARN that only fails at deploy time (it type-checks and\n  `sst dev` runs fine). The fix is `$interpolate`​`` `${bucket.arn}\u002F*` ``. This\n  has caused prod deploy outages. See `references\u002Fauthoring.md` § Outputs.\n- **Migrating a resource between Pulumi *types* should default to two PRs** —\n  Pulumi creates-before-destroys, so for a uniqueness-constrained AWS name\n  (bucket, IAM role, gateway) the old resource still owns it and the create\n  fails with `ConflictException`. Two sequential deploys (teardown, then\n  recreate) is the conservative default; `aliases:` \u002F `pulumi import` \u002F state\n  surgery can bridge identity in some cases but only with a reviewed plan. See\n  `references\u002Fdeploy-and-troubleshoot.md` § Migrations.\n- **Prefer typed `sst.aws.*` \u002F `aws.*` resources over the\n  `aws.cloudcontrol.Resource` escape hatch.** CloudControl outputs are\n  stringly-typed and `oneOf` fields don't patch cleanly. Use it only when no\n  typed resource exists yet, and migrate off it when one ships.\n\n**Project-specific defaults — adopt for consistency, but confirm per repo:**\n\n- **Region `ap-northeast-1`**, `home: \"aws\"`, and `defaultTags` carrying\n  `Project` \u002F `Stage` \u002F `ManagedBy: \"sst\"`.\n- **Stage-gated lifecycle**: `removal: stage === \"prod\" ? \"retain\" : \"remove\"`\n  and `protect: stage === \"prod\"` so prod resources survive a stack tear-down\n  and non-prod previews clean up.\n- **SSM Parameter Store as the out-of-graph contract** under a\n  `\u002F{app}\u002F{stage}\u002F{domain}\u002F...` prefix — for consumers that aren't in the\n  Pulumi graph (CI scripts, sibling apps, operators). For *same-app* Lambdas,\n  prefer SST `link:` (it wires a real dependency edge and grants IAM); don't\n  route same-app sharing through SSM. See `references\u002Fauthoring.md` § Sharing.\n- **Lazy `await import(\".\u002Finfra\u002F\u003Cmodule>\")` inside `run()`** so `sst dev`\n  hot-reload stays light. (For testing, a module export still runs its top-level\n  `new sst.aws.*` unless it's wrapped in a factory function — see\n  `references\u002Ftesting.md` for how to test infra.)\n- **Source-level Vitest tests** on every infra module — a lightweight,\n  house-style regression net asserting on the *source text* (resource names,\n  index shapes, IAM scopes). It's a deliberate choice, not an SST limit: Pulumi\n  *does* support runtime mocks (`@pulumi\u002Fpulumi\u002Fruntime`) for behavioral graph\n  tests when a module has real logic. Source assertions don't replace a\n  preview-deploy + smoke test. See `references\u002Ftesting.md`.\n- **An observability gate**: every new Lambda\u002Fqueue\u002Fschedule gets an alarm and\n  structured logging before merge. Whether you enforce this depends on the\n  project, but it's cheap insurance. See `references\u002Fdeploy-and-troubleshoot.md`\n  § Observability.\n\nWhen you introduce a convention, say which bucket it's in (\"this is universal\"\nvs \"matching this repo's house style\") so the user can override the\nproject-specific ones deliberately.\n\n## Working rhythm\n\n1. **Orient** (above) — map config, modules, tests, tooling.\n2. **Verify syntax** with Context7 \u002F AWS docs MCP if anything is non-obvious.\n   Don't guess at a component's option name.\n3. **Author** the resource\u002Fmodule following `references\u002Fauthoring.md`. Match the\n   surrounding file's commenting density and naming — these projects comment the\n   *why* heavily, and a terse one-liner in a heavily-annotated file reads as a\n   regression.\n4. **Test** — add or update source-level assertions (`references\u002Ftesting.md`) and\n   run `npx vitest` (or the repo's `test` script). Run `npx sst diff` and\u002For\n   `tsc --noEmit` to catch type and plan errors before deploying.\n5. **Deploy\u002Foperate** per `references\u002Fdeploy-and-troubleshoot.md`. Confirm the\n   target account with `aws sts get-caller-identity` before any `sst deploy`.\n6. **Clean up** any exported state files — they contain account IDs and ARNs and\n   must not linger in `\u002Ftmp` or chat history.\n\n## What good looks like\n\n- The change is the smallest diff that satisfies the requirement, in the right\n  `infra\u002F` module, wired into `run()` in dependency order.\n- Every Lambda gets the right runtime via the global transform (you didn't\n  hand-set `runtime` unless intentionally diverging — e.g. a Python function).\n- Cross-resource references use `link:` (in-graph) and\u002For `$interpolate`-scoped\n  IAM; outputs other tools consume are published to SSM under the stage prefix.\n- New infra has a matching source-level test, and the existing suite stays green.\n- You confirmed AWS-side facts via the docs MCP and SST\u002FPulumi syntax via\n  Context7 rather than relying on recall.\n- Anything irreversible (deploy, `sst remove`, a resource-type migration) was\n  flagged to the user with the account it targets, and migrations were planned\n  as two PRs, not one.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"critical","https:\u002F\u002Fgithub.com\u002Fzxkane\u002Faws-skills\u002Ftree\u002Fmain\u002Fplugins\u002Faws-iac\u002Fskills\u002Faws-sst-development",1782864000000,"zxkane\u002Faws-skills","community","https:\u002F\u002Fgithub.com\u002Fzxkane\u002Faws-skills\u002Fblob\u002Fmain\u002FLICENSE","main","a4404a75dc81d6b7e58c5906b6aaffbcb5e84747","Claude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Faws-sst-development",0,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills","https:\u002F\u002Fgithub.com\u002FMHassan0000","https:\u002F\u002Fhassanyousaf.vercel.app","Full Stack Developer building web apps, SaaS, AI systems, and automations. Passionate about clean code, UI\u002FUX, backend systems, and turning ideas into products.","2026-08-07 20:42:05",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add MHassan0000\u002FSkills --skill aws-sst-development",{"tool":45,"command":46},"bunx","bunx skills add MHassan0000\u002FSkills --skill aws-sst-development",{"tool":48,"command":49},"pnpm","pnpm dlx skills add MHassan0000\u002FSkills --skill aws-sst-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Faws-sst-development\u002FSKILL.md",true,[],[54,61,68,75,84,92],{"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},"01M7AGBX58S04DX8DKKME8N311","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fvercel-react-best-practices\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},"01M7AGBREE890608Z7YDMAKH27","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells and produce more human-like writing.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fstop-slop\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},"01M7AGAS972A2AN7Q5EW8HEAXK","ogilvy-copywriting","Apply David Ogilvy's advertising principles when writing or reviewing copy, headlines, product descriptions, landing pages, ads, emails, or any persuasive text. Use when the goal is copy that sells, not copy that wins awards. Covers positioning, headlines, promises, brand voice, long-form copy, and visual logic. Source: How to Create Advertising That Sells (1972) + Ogilvy on Advertising.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fogilvy\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":79,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AGAF12803G5JPVMK79AYJB","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7AG88WWVWCGJY9WA9CH7EY4","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7AG7ZTNV7XQCWDQ9674FBYB","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[]]