fix(sequence): dash OAuth returns and align type-sequence docs (#14)
Polish after #13: 401 and retry 200 use dashed return strokes on all three OAuth examples; first API activation bar covers the happy-path return; type-sequence return rules no longer contradict the message table; README quickstart names bearer+refresh rather than a full OAuth handshake. verify-sequence-oauth.py now checks dashed returns and activation height.
This commit is contained in:
@@ -179,9 +179,9 @@ open ~/.claude/skills/diagram-design/assets/index.html
|
||||
# In Claude Code, just ask:
|
||||
# "Make me an architecture diagram of my app: frontend, backend, database, Redis cache."
|
||||
# "I need a quadrant showing Q2 projects by impact vs effort."
|
||||
# "Give me a sequence diagram of the OAuth handshake."
|
||||
# (branching token refresh uses the ALT combined-fragment grammar in type-sequence.md;
|
||||
# see assets/example-sequence-oauth.html)
|
||||
# "Give me a sequence of a bearer call with token refresh on 401."
|
||||
# (branching refresh uses the ALT combined-fragment grammar in type-sequence.md;
|
||||
# see assets/example-sequence-oauth.html — not a full authorize-code handshake)
|
||||
```
|
||||
|
||||
Claude will pick the right type, build the HTML, and save it. You can also start from a template directly:
|
||||
|
||||
Reference in New Issue
Block a user