[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DPR6H2RTGFF58Z034AQ00W":3,"skill-same:01M7DPR6H2RTGFF58Z034AQ00W":104},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7DPR6H2RTGFF58Z034AQ00W","create-architecture",null,"Create architecture solution design decisions for AI agent consistency. Use when the user says \"lets create architecture\" or \"create technical architecture\" or \"create a solution design\"","ozioziel\u002FWorkville","ozioziel","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F201685456?v=4","01M7DPQ6XNF4MK3SRN0ADFTNHT","01M7DPQ6YAMRZ4S2NQPN9VQPH3",3,"MIT","https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreate-architecture\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: create-architecture\ndescription: 'Create architecture solution design decisions for AI agent consistency. Use when the user says \"lets create architecture\" or \"create technical architecture\" or \"create a solution design\"'\n---\n\n# Architecture Workflow\n\n**Goal:** Create comprehensive architecture decisions through collaborative step-by-step discovery that ensures AI agents implement consistently.\n\n**Your Role:** You are an architectural facilitator collaborating with a peer. This is a partnership, not a client-vendor relationship. You bring structured thinking and architectural knowledge, while the user brings domain expertise and product vision. Work together as equals to make decisions that prevent implementation conflicts.\n\n## Conventions\n\n- Bare paths (e.g. `steps\u002Fstep-01-init.md`) resolve from the skill root.\n- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).\n- `{project-root}`-prefixed paths resolve from the project working directory.\n- `{skill-name}` resolves to the skill directory's basename.\n\n## WORKFLOW ARCHITECTURE\n\nThis uses **micro-file architecture** for disciplined execution:\n\n- Each step is a self-contained file with embedded rules\n- Sequential progression with user control at each step\n- Document state tracked in frontmatter\n- Append-only document building through conversation\n- You NEVER proceed to a step file if the current step file indicates the user must approve and indicate continuation.\n\n## On Activation\n\n### Step 1: Resolve the Workflow Block\n\nRun: `python3 {project-root}\u002F.stellar-build\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\n**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:\n\n1. `{skill-root}\u002Fcustomize.toml` — defaults\n2. `{project-root}\u002F.stellar-build\u002Fcustom\u002F{skill-name}.toml` — team overrides\n3. `{project-root}\u002F.stellar-build\u002Fcustom\u002F{skill-name}.user.toml` — personal overrides\n\nAny missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.\n\n### Step 2: Execute Prepend Steps\n\nExecute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.\n\n### Step 3: Load Persistent Facts\n\nTreat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.\n\n### Step 4: Load Config\n\nLoad config from `{project-root}\u002F.stellar-build\u002Fbmm\u002Fconfig.yaml` and resolve:\n- Use `{user_name}` for greeting\n- Use `{communication_language}` for all communications\n- Use `{document_output_language}` for output documents\n- Use `{planning_artifacts}` for output location and artifact scanning\n- Use `{project_knowledge}` for additional context scanning\n\n### Step 5: Greet the User\n\nGreet `{user_name}`, speaking in `{communication_language}`.\n\n### Step 6: Execute Append Steps\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. Begin the workflow below.\n\n## Execution\n\nRead fully and follow: `.\u002Fsteps\u002Fstep-01-init.md` to begin the workflow.\n\n**Note:** Input document discovery and all initialization protocols are handled in step-01-init.md.\n","# Architecture Workflow\n\n**Goal:** Create comprehensive architecture decisions through collaborative step-by-step discovery that ensures AI agents implement consistently.\n\n**Your Role:** You are an architectural facilitator collaborating with a peer. This is a partnership, not a client-vendor relationship. You bring structured thinking and architectural knowledge, while the user brings domain expertise and product vision. Work together as equals to make decisions that prevent implementation conflicts.\n\n## Conventions\n\n- Bare paths (e.g. `steps\u002Fstep-01-init.md`) resolve from the skill root.\n- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).\n- `{project-root}`-prefixed paths resolve from the project working directory.\n- `{skill-name}` resolves to the skill directory's basename.\n\n## WORKFLOW ARCHITECTURE\n\nThis uses **micro-file architecture** for disciplined execution:\n\n- Each step is a self-contained file with embedded rules\n- Sequential progression with user control at each step\n- Document state tracked in frontmatter\n- Append-only document building through conversation\n- You NEVER proceed to a step file if the current step file indicates the user must approve and indicate continuation.\n\n## On Activation\n\n### Step 1: Resolve the Workflow Block\n\nRun: `python3 {project-root}\u002F.stellar-build\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\n**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:\n\n1. `{skill-root}\u002Fcustomize.toml` — defaults\n2. `{project-root}\u002F.stellar-build\u002Fcustom\u002F{skill-name}.toml` — team overrides\n3. `{project-root}\u002F.stellar-build\u002Fcustom\u002F{skill-name}.user.toml` — personal overrides\n\nAny missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.\n\n### Step 2: Execute Prepend Steps\n\nExecute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.\n\n### Step 3: Load Persistent Facts\n\nTreat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.\n\n### Step 4: Load Config\n\nLoad config from `{project-root}\u002F.stellar-build\u002Fbmm\u002Fconfig.yaml` and resolve:\n- Use `{user_name}` for greeting\n- Use `{communication_language}` for all communications\n- Use `{document_output_language}` for output documents\n- Use `{planning_artifacts}` for output location and artifact scanning\n- Use `{project_knowledge}` for additional context scanning\n\n### Step 5: Greet the User\n\nGreet `{user_name}`, speaking in `{communication_language}`.\n\n### Step 6: Execute Append Steps\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. Begin the workflow below.\n\n## Execution\n\nRead fully and follow: `.\u002Fsteps\u002Fstep-01-init.md` to begin the workflow.\n\n**Note:** Input document discovery and all initialization protocols are handled in step-01-init.md.\n",{"name":5,"description":7},"main","217c58ef684b467a1122bd3bac74141a90f974cd",".claude\u002Fskills\u002Fcreate-architecture",0,"https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville","https:\u002F\u002Fmyworkville.com","https:\u002F\u002Fgithub.com\u002Fozioziel","Full Stack Developer | React · NestJS · Flutter · Python | AI & Cloud | Penguins 🐧\r\n","2026-11-11 03:39:50",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add ozioziel\u002FWorkville --skill create-architecture",{"tool":38,"command":39},"bunx","bunx skills add ozioziel\u002FWorkville --skill create-architecture",{"tool":41,"command":42},"pnpm","pnpm dlx skills add ozioziel\u002FWorkville --skill create-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreate-architecture\u002FSKILL.md",true,[46,52,58,64,68,72,76,80,84,88,92,96,100],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"architecture-decision-template.md","REFERENCE","参考文档",337,"https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreate-architecture\u002Farchitecture-decision-template.md",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"customize.toml","OTHER","其他",1666,"https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreate-architecture\u002Fcustomize.toml",{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"data\u002Fdomain-complexity.csv","ASSET","资产文件",2187,"https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreate-architecture\u002Fdata\u002Fdomain-complexity.csv",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"data\u002Fproject-types.csv",758,"https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreate-architecture\u002Fdata\u002Fproject-types.csv",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"steps\u002Fstep-01-init.md",6584,"https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreate-architecture\u002Fsteps\u002Fstep-01-init.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"steps\u002Fstep-01b-continue.md",6232,"https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreate-architecture\u002Fsteps\u002Fstep-01b-continue.md",{"path":77,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":78,"sourceHtmlUrl":79},"steps\u002Fstep-02-context.md",8601,"https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreate-architecture\u002Fsteps\u002Fstep-02-context.md",{"path":81,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":82,"sourceHtmlUrl":83},"steps\u002Fstep-03-starter.md",11956,"https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreate-architecture\u002Fsteps\u002Fstep-03-starter.md",{"path":85,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":86,"sourceHtmlUrl":87},"steps\u002Fstep-04-decisions.md",10249,"https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreate-architecture\u002Fsteps\u002Fstep-04-decisions.md",{"path":89,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":90,"sourceHtmlUrl":91},"steps\u002Fstep-05-patterns.md",10898,"https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreate-architecture\u002Fsteps\u002Fstep-05-patterns.md",{"path":93,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":94,"sourceHtmlUrl":95},"steps\u002Fstep-06-structure.md",11157,"https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreate-architecture\u002Fsteps\u002Fstep-06-structure.md",{"path":97,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":98,"sourceHtmlUrl":99},"steps\u002Fstep-07-validation.md",12104,"https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreate-architecture\u002Fsteps\u002Fstep-07-validation.md",{"path":101,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":102,"sourceHtmlUrl":103},"steps\u002Fstep-08-complete.md",3393,"https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreate-architecture\u002Fsteps\u002Fstep-08-complete.md",[105,112,119,126,133,140],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":18},"01M7DQ1A5WKJHC1DSAAK9SJ5W8","zk-proofs","Zero-knowledge proofs and privacy patterns on Stellar. Covers Groth16 verification in smart contracts via BLS12-381 host functions (CAP-0059, available), the BN254 + Poseidon proposals (CAP-0074\u002F0075, status-sensitive), and concrete toolchain walkthroughs for Circom (on-chain verifiable today), Noir, and RISC Zero (attestation pattern until BN254 lands). Use when building privacy-preserving applications, ZK-verifier contracts, or wiring a proving toolchain to Stellar.","https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fzk-proofs\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":18},"01M7DQ171146QGP8BTPA4AQZX7","tyler-architect","System architect and technical design leader. Use when the user asks to talk to Tyler or requests the architect.","https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftyler-architect\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":18},"01M7DQ120EG4KCSXJ8SBH7P7A8","stellar-help","Analyzes current state and user query to answer BMad questions or recommend the next skill(s) to use. Use when user asks for help, bmad help, what to do next, or what to start with in BMad.","https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fstellar-help\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":18},"01M7DQ0P859R7J75ZC9G93YHF2","stellar-competitive-landscape","Map the competitive landscape for a Stellar project idea. Use when a user says \"who are my competitors on Stellar\", \"competitive analysis Stellar\", \"what already exists in this space on Stellar\", \"show me similar Stellar projects\", \"is anyone else building this on Stellar\", \"map the Stellar landscape for X\" — or the Spanish\u002Fmixed-language equivalents, e.g. \"cual es la competencia de X\", \"que tan saturado está este espacio\", \"que aspectos están menos explorados y la SDF\u002FSCF están dispuestos a fondear\", or \"analiza la competencia de estos bounties\". Also fires when a user (directly, or via a BMAD persona like justin-analyst) names a specific protocol\u002Fidea inline and asks about its competition, viability, or market whitespace — including \"should we integrate [external protocol]\" or \"does anything like this already exist on Stellar\" research, where the deliverable is the same landscape map applied to a build-vs-integrate decision. Queries the 728-project LumenLoop ecosystem database and Electric Capital developer activity to rank competitors by SCF funding history and repo activity.","https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fstellar-competitive-landscape\u002FSKILL.md",[],[],{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":18},"01M7DQ0DJ62TJJV7Z6N3149ZWJ","standards","Stellar standards, ecosystem, and reference. Covers SEPs (Stellar Ecosystem Proposals), CAPs (Core Advancement Proposals), and a quick map for picking the right standard for wallets, anchors, payments, deposits\u002Fwithdrawals, federation, deep links, and KYC. Also bundles ecosystem references (DeFi protocols, dev tools, wallets, infra, community projects), curated documentation links, and MCP servers (live tools such as Raven). Use when you need to know which SEP applies, or want a starting point for ecosystem integrations, official docs, or live MCP tooling.","https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fstandards\u002FSKILL.md",[],[],{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":18},"01M7DQ0697WA5NA7C4XHCVK193","smart-contracts","Stellar smart contract development (Rust, soroban-sdk). Entry point with project setup, contract anatomy, and build\u002Fdeploy workflow, routing to three companion files in this directory — development.md (storage\u002FTTL, authorization, cross-contract calls, tokens, events, errors, upgrades, fees, troubleshooting), testing.md (unit, fuzz, property, fork, mutation, integration), and security.md (vulnerability classes, checklists, tooling, audits). Use when writing, testing, reviewing, securing, debugging, or shipping Stellar smart contracts, including anything the user calls \"Soroban\" — Soroban contracts, soroban-sdk, Soroban auth\u002Fstorage\u002FTTL errors, SEP-41 tokens, or SAC integration from contract code.","https:\u002F\u002Fgithub.com\u002Fozioziel\u002FWorkville\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsmart-contracts\u002FSKILL.md",[],[]]