[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B2Z0FQDCF4GP5XFSZTNQZ9":3,"skill-same:01M7B2Z0FQDCF4GP5XFSZTNQZ9":70},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7B2Z0FQDCF4GP5XFSZTNQZ9","hamster-database",null,"Supabase database patterns for Hamster Studio. Use when working with schemas, migrations, RLS policies, SQL functions, or database queries. Essential for any database-related work.","gethamster\u002Fskills","gethamster","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F215697643?v=4","01M7B2R6PGB3SDZZ71E0WE2S74","Hamster","01M7B2R6Q21HWJRXZZWB78BNDG",4,"MIT","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Fhamster-database\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: hamster-database\ndescription: \"Supabase database patterns for Hamster Studio. Use when working with schemas, migrations, RLS policies, SQL functions, or database queries. Essential for any database-related work.\"\nversion: \"1.1.0\"\n---\n\n# Hamster Database Patterns\n\n## Overview\n\nDatabase conventions for the Hamster Studio multi-tenant SaaS. Covers Supabase schema design, RLS policies, migrations, and SQL functions.\n\n## When to Apply\n\n- Creating or modifying database tables\n- Writing RLS policies\n- Creating database functions or triggers\n- Running migrations\n- Writing SQL queries\n\n## Quick Reference\n\n| Task | Pattern | Reference |\n| --- | --- | --- |\n| Create table | Enable RLS, add `account_id`, use triggers | `references\u002Frules\u002Fschema-patterns.md` |\n| Add RLS policy | Use helper functions, test all operations | `references\u002Frules\u002Frls-policies.md` |\n| Create migration | Use `supabase:db:diff`, never copy manually | `references\u002Frules\u002Fmigration-workflow.md` |\n| Write function | SECURITY INVOKER, set `search_path = ''` | `references\u002Frules\u002Fsql-functions.md` |\n| SQL style | Lowercase keywords, snake_case names | `references\u002Frules\u002Fsql-style-guide.md` |\n\n## Core Architecture\n\n### Multi-Tenant Data Model\n\n```\naccounts (personal + team)\n    ↓ account_id FK\nfeature_tables (all user data)\n    ↓ RLS policies\nhas_role_on_account() \u002F has_permission()\n```\n\n**Rule**: ALL feature data MUST have `account_id` foreign key to `accounts`.\n\n### RLS Helper Functions\n\n| Function | Use Case | Example |\n| --- | --- | --- |\n| `has_role_on_account(account_id)` | Team membership | SELECT, basic access |\n| `has_permission(user_id, account_id, permission)` | Specific capability | INSERT, UPDATE, DELETE |\n| `is_account_owner(account_id)` | Owner-only actions | Destructive operations |\n\n### Standard Table Template\n\n```sql\ncreate table if not exists public.my_feature (\n  id uuid unique not null default extensions.uuid_generate_v4(),\n  account_id uuid references public.accounts(id) on delete cascade not null,\n  created_at timestamptz default now() not null,\n  updated_at timestamptz default now() not null,\n  created_by uuid references auth.users(id),\n  updated_by uuid references auth.users(id),\n  -- feature columns\n  primary key (id)\n);\n\n-- CRITICAL: Always enable RLS\nalter table public.my_feature enable row level security;\n\n-- Revoke defaults, grant specific\nrevoke all on public.my_feature from authenticated, service_role;\ngrant select, insert, update, delete on public.my_feature to authenticated;\n\n-- Add standard triggers\ncreate trigger set_timestamps\n  before insert or update on public.my_feature\n  for each row execute function public.trigger_set_timestamps();\n\ncreate trigger set_user_tracking\n  before insert or update on public.my_feature\n  for each row execute function public.trigger_set_user_tracking();\n```\n\n## Migration Workflow (CRITICAL)\n\n**ALWAYS** use the diff tool, never copy schema files:\n\n```bash\n# 1. Create\u002Fedit schema file\napps\u002Fweb\u002Fsupabase\u002Fschemas\u002FNN-my-feature.sql\n\n# 2. Reset database to apply schemas\npnpm supabase:web:reset\n\n# 3. Generate migration from diff\npnpm --filter web supabase:db:diff -f my-feature-name\n\n# 4. Generate TypeScript types\npnpm supabase:web:typegen\n```\n\n> Migration filenames follow `YYYYMMDDHHmmss_description.sql` in UTC. `db:diff` writes the prefix automatically; if a CI ordering check rejects your migration, rename with `date -u +%Y%m%d%H%M%S` (the `-u` flag is required). See `references\u002Frules\u002Fmigration-workflow.md`.\n\n## RLS Policy Patterns\n\n### Personal + Team Access (Most Common)\n\n```sql\ncreate policy \"read\" on public.my_feature for select\n  to authenticated using (\n    account_id = (select auth.uid()) or\n    public.has_role_on_account(account_id)\n  );\n```\n\n### Permission-Based Write\n\n```sql\ncreate policy \"write\" on public.my_feature for insert\n  to authenticated with check (\n    public.has_permission(auth.uid(), account_id, 'feature.manage'::app_permissions)\n  );\n```\n\n### UPDATE Requires Both USING and WITH CHECK\n\n```sql\ncreate policy \"update\" on public.my_feature for update\n  to authenticated\n  using (public.has_permission(auth.uid(), account_id, 'feature.manage'::app_permissions))\n  with check (public.has_permission(auth.uid(), account_id, 'feature.manage'::app_permissions));\n```\n\n## Function Security\n\n```sql\ncreate or replace function public.my_function(param uuid)\nreturns setof public.my_table\nlanguage plpgsql\nsecurity invoker  -- Inherit caller's RLS (preferred)\nset search_path = ''  -- Prevent injection\nas $$\nbegin\n  return query select * from public.my_table where id = param;\nend;\n$$;\n\ngrant execute on function public.my_function(uuid) to authenticated;\n```\n\n**Rule**: Use `security definer` ONLY when bypassing RLS is necessary, with explicit auth checks.\n\n## Data Access Patterns\n\nChoose the right approach: **Queries** (default), **Views** (computed), or **Functions** (complex).\n\n| Pattern | Use When | Maintenance Cost |\n| --- | --- | --- |\n| **Query** | Simple CRUD, FK relations, filters | Low (code change) |\n| **View** | Read-only aggregations, UNIONs | Medium (migration) |\n| **Function** | Atomic transactions, complex joins, business logic | High (migration) |\n\n### Use Supabase Queries (Default)\n\nQueries live in code, are easy to modify, and handle FK relationships automatically.\n\n```typescript\n\u002F\u002F FK relationships work - no function needed\nconst { data } = await client\n  .from('brief')\n  .select(`*, document:document!inner(*)`)\n  .eq('account_id', accountId);\n\n\u002F\u002F Join through FK for related data\nconst { data } = await client\n  .from('task_dependencies')\n  .select(`\n    depends_on_task_id,\n    tasks!task_dependencies_depends_on_task_id_fkey (id, title, status)\n  `)\n  .eq('task_id', taskId);\n```\n\n### Use Views\n\nFor read-only computed data, UNIONs, and pre-joined data.\n\n> :warning: **CRITICAL: Views and RLS**\n> \n> Views run with the privileges of the view *creator* by default, **bypassing RLS** on underlying tables. This is a major security risk that has caused data leaks.\n> \n> **ALWAYS** use `security_invoker = true` on views to inherit the *caller's* RLS policies.\n\n```sql\n-- UNION of multiple sources\n-- MUST use security_invoker to enforce RLS on underlying tables\ncreate view public.waitlist_merged with (security_invoker = true) as\nselect ... from waitlist\nunion all\nselect ... from accounts where not exists (...);\n\n-- Pre-joined workspace data\ncreate view public.user_accounts with (security_invoker = true) as\nselect account.id, account.name, membership.account_role\nfrom accounts account\njoin accounts_memberships membership on account.id = membership.account_id\nwhere membership.user_id = auth.uid();\n```\n\n**Why `security_invoker = true` is mandatory:**\n\n- Without it: View runs as creator → RLS bypassed → data leak\n- With it: View runs as caller → RLS enforced → secure\n\n### Use Functions\n\nFor atomic transactions, complex multi-table joins, or business logic.\n\n```sql\n-- Atomic multi-table update (status + positions must succeed together)\ncreate function public.change_status_and_reorder(\n  p_account_id uuid, p_task_id uuid, p_new_status text,\n  p_task_updates jsonb, p_updated_by uuid\n) returns void as $$\nbegin\n  update tasks set status = p_new_status::task_status where id = p_task_id;\n  for rec in select * from jsonb_array_elements(p_task_updates) loop\n    update tasks set position = (rec ->> 'position')::integer\n    where id = (rec ->> 'taskId')::uuid;\n  end loop;\nend;\n$$ language plpgsql;\n```\n\nCall functions with `.rpc()`:\n\n```typescript\nconst { data } = await client.rpc('reorder_briefs', {\n  p_account_id: accountId,\n  p_brief_id: briefId,\n  p_new_position: newPosition,\n});\n```\n\n### Decision Checklist\n\n1. Can Supabase query builder express this? → **Use query**\n2. Is it read-only aggregation\u002FUNION? → **Use view**\n3. Needs atomic multi-table updates? → **Use function**\n4. Needs recursive CTEs or complex joins? → **Use function**\n5. Enforces business invariants? → **Use function (often as trigger)**\n\n**Default to queries. Functions require migrations to change—avoid overusing them.**\n\n## Testing\n\nFor database testing patterns, see the [hamster-database-testing](..\u002Fhamster-database-testing\u002FSKILL.md) skill. It covers:\n\n- **Vitest** — RLS policies, constraints (via Supabase client, multi-user scenarios)\n- **pgTAP** — Triggers, functions, schema assertions (via SQL)\n\n## Key Files\n\n| File | Purpose |\n| --- | --- |\n| `apps\u002Fweb\u002Fsupabase\u002Fschemas\u002F` | Schema definitions (numbered) |\n| `apps\u002Fweb\u002Fsupabase\u002Fmigrations\u002F` | Generated migrations |\n| `apps\u002Fweb\u002Fsupabase\u002FCLAUDE.md` | Detailed database workflow |\n| `packages\u002Fsupabase\u002Fsrc\u002Fdatabase.types.ts` | Generated TypeScript types |\n\n## References\n\n- `references\u002Frules\u002Frls-policies.md` - RLS policy guidelines and examples\n- `references\u002Frules\u002Fmigration-workflow.md` - Migration file conventions\n- `references\u002Frules\u002Fschema-patterns.md` - Table creation patterns\n- `references\u002Frules\u002Fsql-functions.md` - Database function patterns\n- `references\u002Frules\u002Fsql-style-guide.md` - SQL naming and formatting\n","# Hamster Database Patterns\n\n## Overview\n\nDatabase conventions for the Hamster Studio multi-tenant SaaS. Covers Supabase schema design, RLS policies, migrations, and SQL functions.\n\n## When to Apply\n\n- Creating or modifying database tables\n- Writing RLS policies\n- Creating database functions or triggers\n- Running migrations\n- Writing SQL queries\n\n## Quick Reference\n\n| Task | Pattern | Reference |\n| --- | --- | --- |\n| Create table | Enable RLS, add `account_id`, use triggers | `references\u002Frules\u002Fschema-patterns.md` |\n| Add RLS policy | Use helper functions, test all operations | `references\u002Frules\u002Frls-policies.md` |\n| Create migration | Use `supabase:db:diff`, never copy manually | `references\u002Frules\u002Fmigration-workflow.md` |\n| Write function | SECURITY INVOKER, set `search_path = ''` | `references\u002Frules\u002Fsql-functions.md` |\n| SQL style | Lowercase keywords, snake_case names | `references\u002Frules\u002Fsql-style-guide.md` |\n\n## Core Architecture\n\n### Multi-Tenant Data Model\n\n```\naccounts (personal + team)\n    ↓ account_id FK\nfeature_tables (all user data)\n    ↓ RLS policies\nhas_role_on_account() \u002F has_permission()\n```\n\n**Rule**: ALL feature data MUST have `account_id` foreign key to `accounts`.\n\n### RLS Helper Functions\n\n| Function | Use Case | Example |\n| --- | --- | --- |\n| `has_role_on_account(account_id)` | Team membership | SELECT, basic access |\n| `has_permission(user_id, account_id, permission)` | Specific capability | INSERT, UPDATE, DELETE |\n| `is_account_owner(account_id)` | Owner-only actions | Destructive operations |\n\n### Standard Table Template\n\n```sql\ncreate table if not exists public.my_feature (\n  id uuid unique not null default extensions.uuid_generate_v4(),\n  account_id uuid references public.accounts(id) on delete cascade not null,\n  created_at timestamptz default now() not null,\n  updated_at timestamptz default now() not null,\n  created_by uuid references auth.users(id),\n  updated_by uuid references auth.users(id),\n  -- feature columns\n  primary key (id)\n);\n\n-- CRITICAL: Always enable RLS\nalter table public.my_feature enable row level security;\n\n-- Revoke defaults, grant specific\nrevoke all on public.my_feature from authenticated, service_role;\ngrant select, insert, update, delete on public.my_feature to authenticated;\n\n-- Add standard triggers\ncreate trigger set_timestamps\n  before insert or update on public.my_feature\n  for each row execute function public.trigger_set_timestamps();\n\ncreate trigger set_user_tracking\n  before insert or update on public.my_feature\n  for each row execute function public.trigger_set_user_tracking();\n```\n\n## Migration Workflow (CRITICAL)\n\n**ALWAYS** use the diff tool, never copy schema files:\n\n```bash\n# 1. Create\u002Fedit schema file\napps\u002Fweb\u002Fsupabase\u002Fschemas\u002FNN-my-feature.sql\n\n# 2. Reset database to apply schemas\npnpm supabase:web:reset\n\n# 3. Generate migration from diff\npnpm --filter web supabase:db:diff -f my-feature-name\n\n# 4. Generate TypeScript types\npnpm supabase:web:typegen\n```\n\n> Migration filenames follow `YYYYMMDDHHmmss_description.sql` in UTC. `db:diff` writes the prefix automatically; if a CI ordering check rejects your migration, rename with `date -u +%Y%m%d%H%M%S` (the `-u` flag is required). See `references\u002Frules\u002Fmigration-workflow.md`.\n\n## RLS Policy Patterns\n\n### Personal + Team Access (Most Common)\n\n```sql\ncreate policy \"read\" on public.my_feature for select\n  to authenticated using (\n    account_id = (select auth.uid()) or\n    public.has_role_on_account(account_id)\n  );\n```\n\n### Permission-Based Write\n\n```sql\ncreate policy \"write\" on public.my_feature for insert\n  to authenticated with check (\n    public.has_permission(auth.uid(), account_id, 'feature.manage'::app_permissions)\n  );\n```\n\n### UPDATE Requires Both USING and WITH CHECK\n\n```sql\ncreate policy \"update\" on public.my_feature for update\n  to authenticated\n  using (public.has_permission(auth.uid(), account_id, 'feature.manage'::app_permissions))\n  with check (public.has_permission(auth.uid(), account_id, 'feature.manage'::app_permissions));\n```\n\n## Function Security\n\n```sql\ncreate or replace function public.my_function(param uuid)\nreturns setof public.my_table\nlanguage plpgsql\nsecurity invoker  -- Inherit caller's RLS (preferred)\nset search_path = ''  -- Prevent injection\nas $$\nbegin\n  return query select * from public.my_table where id = param;\nend;\n$$;\n\ngrant execute on function public.my_function(uuid) to authenticated;\n```\n\n**Rule**: Use `security definer` ONLY when bypassing RLS is necessary, with explicit auth checks.\n\n## Data Access Patterns\n\nChoose the right approach: **Queries** (default), **Views** (computed), or **Functions** (complex).\n\n| Pattern | Use When | Maintenance Cost |\n| --- | --- | --- |\n| **Query** | Simple CRUD, FK relations, filters | Low (code change) |\n| **View** | Read-only aggregations, UNIONs | Medium (migration) |\n| **Function** | Atomic transactions, complex joins, business logic | High (migration) |\n\n### Use Supabase Queries (Default)\n\nQueries live in code, are easy to modify, and handle FK relationships automatically.\n\n```typescript\n\u002F\u002F FK relationships work - no function needed\nconst { data } = await client\n  .from('brief')\n  .select(`*, document:document!inner(*)`)\n  .eq('account_id', accountId);\n\n\u002F\u002F Join through FK for related data\nconst { data } = await client\n  .from('task_dependencies')\n  .select(`\n    depends_on_task_id,\n    tasks!task_dependencies_depends_on_task_id_fkey (id, title, status)\n  `)\n  .eq('task_id', taskId);\n```\n\n### Use Views\n\nFor read-only computed data, UNIONs, and pre-joined data.\n\n> :warning: **CRITICAL: Views and RLS**\n> \n> Views run with the privileges of the view *creator* by default, **bypassing RLS** on underlying tables. This is a major security risk that has caused data leaks.\n> \n> **ALWAYS** use `security_invoker = true` on views to inherit the *caller's* RLS policies.\n\n```sql\n-- UNION of multiple sources\n-- MUST use security_invoker to enforce RLS on underlying tables\ncreate view public.waitlist_merged with (security_invoker = true) as\nselect ... from waitlist\nunion all\nselect ... from accounts where not exists (...);\n\n-- Pre-joined workspace data\ncreate view public.user_accounts with (security_invoker = true) as\nselect account.id, account.name, membership.account_role\nfrom accounts account\njoin accounts_memberships membership on account.id = membership.account_id\nwhere membership.user_id = auth.uid();\n```\n\n**Why `security_invoker = true` is mandatory:**\n\n- Without it: View runs as creator → RLS bypassed → data leak\n- With it: View runs as caller → RLS enforced → secure\n\n### Use Functions\n\nFor atomic transactions, complex multi-table joins, or business logic.\n\n```sql\n-- Atomic multi-table update (status + positions must succeed together)\ncreate function public.change_status_and_reorder(\n  p_account_id uuid, p_task_id uuid, p_new_status text,\n  p_task_updates jsonb, p_updated_by uuid\n) returns void as $$\nbegin\n  update tasks set status = p_new_status::task_status where id = p_task_id;\n  for rec in select * from jsonb_array_elements(p_task_updates) loop\n    update tasks set position = (rec ->> 'position')::integer\n    where id = (rec ->> 'taskId')::uuid;\n  end loop;\nend;\n$$ language plpgsql;\n```\n\nCall functions with `.rpc()`:\n\n```typescript\nconst { data } = await client.rpc('reorder_briefs', {\n  p_account_id: accountId,\n  p_brief_id: briefId,\n  p_new_position: newPosition,\n});\n```\n\n### Decision Checklist\n\n1. Can Supabase query builder express this? → **Use query**\n2. Is it read-only aggregation\u002FUNION? → **Use view**\n3. Needs atomic multi-table updates? → **Use function**\n4. Needs recursive CTEs or complex joins? → **Use function**\n5. Enforces business invariants? → **Use function (often as trigger)**\n\n**Default to queries. Functions require migrations to change—avoid overusing them.**\n\n## Testing\n\nFor database testing patterns, see the [hamster-database-testing](..\u002Fhamster-database-testing\u002FSKILL.md) skill. It covers:\n\n- **Vitest** — RLS policies, constraints (via Supabase client, multi-user scenarios)\n- **pgTAP** — Triggers, functions, schema assertions (via SQL)\n\n## Key Files\n\n| File | Purpose |\n| --- | --- |\n| `apps\u002Fweb\u002Fsupabase\u002Fschemas\u002F` | Schema definitions (numbered) |\n| `apps\u002Fweb\u002Fsupabase\u002Fmigrations\u002F` | Generated migrations |\n| `apps\u002Fweb\u002Fsupabase\u002FCLAUDE.md` | Detailed database workflow |\n| `packages\u002Fsupabase\u002Fsrc\u002Fdatabase.types.ts` | Generated TypeScript types |\n\n## References\n\n- `references\u002Frules\u002Frls-policies.md` - RLS policy guidelines and examples\n- `references\u002Frules\u002Fmigration-workflow.md` - Migration file conventions\n- `references\u002Frules\u002Fschema-patterns.md` - Table creation patterns\n- `references\u002Frules\u002Fsql-functions.md` - Database function patterns\n- `references\u002Frules\u002Fsql-style-guide.md` - SQL naming and formatting\n",{"name":5,"version":24,"description":7},"1.1.0","main","fe3bb1476c3ec23d8a366eac0fa8cd9f0852360a","skills\u002F.experimental\u002Fhamster-database",0,"https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills","https:\u002F\u002Fgithub.com\u002Fgethamster","https:\u002F\u002Ftryhamster.com","We're building the AI-native future of work, unlocking the promised acceleration for your whole team, from idea to impact.","2026-11-05 11:33:33",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add gethamster\u002Fskills --skill hamster-database",{"tool":40,"command":41},"bunx","bunx skills add gethamster\u002Fskills --skill hamster-database",{"tool":43,"command":44},"pnpm","pnpm dlx skills add gethamster\u002Fskills --skill hamster-database","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Fhamster-database\u002FSKILL.md",true,[48,54,58,62,66],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Frules\u002Fmigration-workflow.md","REFERENCE","参考文档",5614,"https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Fhamster-database\u002Freferences\u002Frules\u002Fmigration-workflow.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Frules\u002Frls-policies.md",8248,"https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Fhamster-database\u002Freferences\u002Frules\u002Frls-policies.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Frules\u002Fschema-patterns.md",4506,"https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Fhamster-database\u002Freferences\u002Frules\u002Fschema-patterns.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Frules\u002Fsql-functions.md",4611,"https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Fhamster-database\u002Freferences\u002Frules\u002Fsql-functions.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Frules\u002Fsql-style-guide.md",4490,"https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Fhamster-database\u002Freferences\u002Frules\u002Fsql-style-guide.md",[71,78,85,92,99,106],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7B5MWYW0KE251276S56KQDZ","writing-waterfall-requirements-documents","Write a waterfall requirements document: elicit, structure and review testable, traceable requirements, then baseline the specification before design.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-waterfall-requirements-documents\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7B5MRCXWWPKREPB1CHQ7H90","writing-vision-and-values-statements","Write a V2MOM vision a reader can test and a ranked list of values that settles real tradeoffs, so the rest of the document has a clear anchor.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-vision-and-values-statements\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7B5MKH2CH22YZAHQW3080VQ","writing-system-prompts-for-claude","Write Claude prompts and CLAUDE.md files that supply exact inputs, scope the task, and define done so the first attempt can be checked.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-system-prompts-for-claude\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":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7B5ME1Y3X9RNRKP5HKHKACZ","writing-page-specific-website-copy","Website copywriting by page type: write homepage, landing page, pricing page and feature page copy that fits each page's visitor and single job.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-page-specific-website-copy\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7B5M8MQNM8MN8PYH6BVWJ2B","writing-internal-press-releases","How to write an internal press release: the one-page working backwards press release that opens a PR\u002FFAQ document before anything is built.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-internal-press-releases\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7B5M3P3YH1XF37R8PWXXSBK","writing-email-sequences-that-sell","Email sequence copywriting for nurture and sales: give each email one job, write clear subject lines, and close with one specific call to action.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-email-sequences-that-sell\u002FSKILL.md",[],[]]