morphy-ax
Skill40 starsChanged 4 days agoApache-2.0View on GitHub
Use when changing Morphy AX shared agent-experience state, semantic assessment presentation, performance budgets, or cross-modal compatibility.
In this repository69 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hushh-webapp/AGENTS.mdAGENTS.md
- impeccableSkill
- agent-orchestration-governanceSkill
- analytics-observability-governanceSkill
- animateSkill
- animation-vocabularySkill
- apple-designSkill
- autonomous-rca-governanceSkill
- backend-agents-operonsSkill
- backend-api-contractsSkill
- backend-runtime-governanceSkill
- backendSkill
- brandkitSkill
- client-env-paritySkill
- codex-skill-authoringSkill
- comms-communitySkill
- context-refreshSkill
- contributor-onboardingSkill
- docs-governanceSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- founder-brief-curationSkill
- frontend-architectureSkill
- frontend-cache-coherenceSkill
- frontend-design-systemSkill
- frontend-native-surface-mapperSkill
- frontendSkill
- frontend-surface-placementSkill
- future-plannerSkill
- github-contribution-governanceSkill
- hushh-consent-mcpSkill
- hushh-icon-themeSkill
- iam-consent-governanceSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- improve-animationsSkill
- industrial-brutalist-uiSkill
- kai-test-account-resetSkill
- less-text-karma-jiSkill
- mcp-developer-surfaceSkill
- mobile-nativeSkill
- mobile-parity-auditSkill
- mobile-plugin-contractsSkill
- one-voice-governanceSkill
- oss-license-governanceSkill
- pdf-artifact-generationSkill
- pick-ui-librarySkill
- pkm-upgrade-rehearsalSkill
- planning-boardSkill
- pr-governance-reviewSkill
- profile-uiSkill
- prototypeSkill
- puppy-one-harnessSkill
- quality-contractsSkill
- release-ios-appstoreSkill
- repo-contextSkill
- repo-operationsSkill
- review-animationsSkill
- reviewer-app-testingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Avoid overlap with frontend-design-system, one-voice-governance, and backend-agents-operons.
- Distinctive: line 52
Verify the existing runtime, voice FSM, route playbook, and generated action authority before changing AX.
- Very specific: line 53
Keep Morphy AX pure, redacted, memoizable, and hosted by AgentRuntimeStateProvider.
- Very specific: line 57
Treat trusted_activation_required browser actions as exact Agent Bar continuations over mounted handlers, not redirect or popup-broker …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Morphy AX
Purpose and Trigger
- Primary scope:
morphy-agent-experience - Trigger on Morphy AX snapshots, active interaction layers, presentation derivation, semantic-assessment validation, compatibility projections, or AX performance budgets.
- Avoid overlap with
frontend-design-system,one-voice-governance, andbackend-agents-operons.
Coverage and Ownership
- Role:
spoke - Owner family:
frontend
Owned repo surfaces:
hushh-webapp/lib/morphy-axdocs/development/quality/morphy-agent-experience.md
Non-owned surfaces:
hushh-webapp/lib/voiceconsent-protocol/hushh_mcp/agentshushh-webapp/lib/morphy-ux
Do Use
- Shared, redacted agent-experience snapshot, active-layer composition, and presentation contracts.
- Intelligence-assessment validation and compatibility/non-regression budgets.
- Cross-modal AX behavior that reuses the existing runtime owner and action gateway.
Do Not Use
- Voice action authoring, generated gateway changes, or ADK orchestration ownership.
- Visual primitive work owned by Morphy UX.
- A second React provider, store, router, action registry, DOM observer, or model-facing route tool.
Read First
docs/development/quality/design.mddocs/development/quality/morphy-agent-experience.mddocs/architecture/one/one-voice-runtime-architecture.mddocs/development/quality/frontend-ui-architecture-map.mddocs/architecture/finance/kai-action-gateway-vnext.md
Workflow
- Verify the existing runtime, voice FSM, route playbook, and generated action authority before changing AX.
- Keep Morphy AX pure, redacted, memoizable, and hosted by
AgentRuntimeStateProvider. - Let intelligence assess meaning; deterministic code may validate, reject, normalize, and enforce authority only.
- Compose authored
route,chrome, andinteraction_layerpublishers; expose only the top effective inventory and remove stale owner leases on route change. - Require exact generated dismiss/cancel actions, focus-restored settlement, and declared Agent continuity; never synthesize click or Escape behavior.
- Treat
trusted_activation_requiredbrowser actions as exact Agent Bar continuations over mounted handlers, not redirect or popup-broker fallbacks. - Preserve
OneVoiceContextSnapshotthrough an explicit compatibility projection while migration is active. - Benchmark the same fixtures flag-off and flag-on; block wrong-layer actions, unsafe fallbacks, or budget regressions.
- Route voice, backend-agent, design-system, docs, or quality changes to their owning skills.
Handoff Rules
- Broad frontend work routes to
frontend. - Voice/action contracts route to
one-voice-governance. - ADK or product-agent changes route to
backend-agents-operons. - Visual primitives route to
frontend-design-system; verification policy routes toquality-contracts.
Required Checks
cd hushh-webapp && npm run verify:morphy-ax
cd hushh-webapp && npm run typecheck
cd hushh-webapp && npm run verify:voice-gateway
cd hushh-webapp && npm run verify:design-system
cd consent-protocol && python3 -m pytest tests/test_onboarding_goal_agent.py tests/test_one_adk_agent_tree.py -q
./bin/hushh docs verifyDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

