organization
The organization's settled decisions. Consult before asking the user any policy question, and before naming a provider or technology at design time.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-11
- Stars
- ★ 24
- Forks
- 24
01 前言 Front Matter
- name
- organization
- metadata
- { "aep": { "kind": "org", "audience": [ "design" ] } }
- description
- The organization's settled decisions. Consult before asking the user any policy question, and before naming a provider or technology at design time.
03 SKILL.md 正文
Every section below is settled — this organization has already decided it. Anything not below is open: interview for it normally.
- In an interview (start, interview, refine): answer from the settled
section and move on, recording it as a line carrying the source tag
[org default](prd-contract). The user can override it in chat like any other decision, and the override wins. - At design time: a settled section pins its provider or technology outright. A settled capability gets no suggestions list — it is a given, not a choice left to the user.
Authentication & identity
Every web app signs its users in via SSO through Thunder, the platform IDP. Thunder is available as a dependency.
Security & compliance
security-design owns how a permission catalog is derived and what
specs/design/security.json may say. This section is a pointer, not a
specification: it holds only the calls that skill deliberately leaves to the
organization, because they are about the org's own shared directory rather than
about one project. A filled line is settled and is never asked at design time;
an empty one leaves the call to security-design.
| The call | This organization's answer |
|---|---|
| May a design introduce a new org group? | Yes, but only where list_groups shows no existing group is already those people. |
| Groups to prefer, by name. | (none — the directory is the list) |
| Groups a role may never be assigned to. | Administrators. It administers the platform, not any generated app. |
| Is self-service enrolment permitted? | Only where the PRD describes people who sign themselves up. |
Changing how a design derives groups, roles and scopes starts here: this is the
org-editable surface, and security-design is platform-owned and read-only in
the console. A change it cannot express is a change to that skill.
Technology stack
- Web apps: TypeScript + React, single-page app.
- Services and APIs: Ballerina.
UI design system
oxygen-ui-design-system
That is the name of a skill in this library, and it is the single authority for this organization's web-app UI — components, layout, styling, theming, and the verification step a web-app build owes it. This section is a pointer, not a specification: what the design system requires is stated in that skill and is never restated here, so the two can never disagree.
To adopt a different design system, change the name above and make sure a skill by that name exists. Those are the only edits — nothing else in the library names a design system. Leave this section empty to run with no design system at all; web-app builds then carry only the stack skills.
04 同仓库更多 Skills
validation-task
Load when working a VALIDATION task dispatched by WSO2 Labs Agentic Engineer — judging a deployed version against its acceptance criteria.
thunder-authentication
Apply when a component sits on the project's sign-in — a SPA whose users authenticate through the auth platform-resource dependency, or a protected backend those signed-in users call.
task-planning
Use when planning a version's build from a design — the plan turn that writes the build's checklist with planBuild, one item per feature the version carries in build order, after a Foundation item when the version needs one.
start
Use when kicking off a project from its idea — the product pass that agrees the feature list and writes the product page, the product-wide page and a stub per feature — or re-running /start on a project that already has requirements.
security-design
Write specs/design/security.json when a design has sign-in, permissions, roles or test users — the permission catalog every API operation is gated on.
resolve-dependency
Use for taking one external dependency from open to resolved — `/resolve-dependency <name> [answer]` names it and may carry the provider the user chose; `/resolve-dependencies` walks every open one in turn. Ask which provider (their suggestions as options; never choose for them), get its interface on disk (found, uploaded from the card, or assumed under the authorization the card records), then derive the config keys.