feat: add initial skill authoring workspace
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
75
skills/zhihu-navigate/references/routes-and-targets.md
Normal file
75
skills/zhihu-navigate/references/routes-and-targets.md
Normal file
@@ -0,0 +1,75 @@
|
||||
# Routes And Targets
|
||||
|
||||
This skill is derived from the remote navigation catalog in `assets/zhihu_navigation_pages.source.json`.
|
||||
|
||||
## Current Scope
|
||||
|
||||
- Routes: 13
|
||||
- Components: 53
|
||||
- Flows: 16
|
||||
- Targets: 69
|
||||
|
||||
## Model
|
||||
|
||||
- `route`: direct page destination with a known URL
|
||||
- `component`: clickable entry, tab, button, or menu control
|
||||
- `flow`: multi-step sequence composed from routes and components
|
||||
- `target`: user-facing entry point that resolves to exactly one route, component, or flow
|
||||
|
||||
## Representative Routes
|
||||
|
||||
- `home`
|
||||
- `hot_list`
|
||||
- `notifications_page`
|
||||
- `messages_page`
|
||||
- `search_results_page`
|
||||
- `creator_home`
|
||||
- `write_article`
|
||||
|
||||
## Representative Components
|
||||
|
||||
- `top_nav_home`
|
||||
- `top_nav_hot`
|
||||
- `top_nav_creator`
|
||||
- `top_nav_notifications`
|
||||
- `top_nav_avatar_menu`
|
||||
- `notifications_tab_replies`
|
||||
- `messages_all_tab`
|
||||
|
||||
## Representative Flows
|
||||
|
||||
- `open_avatar_menu`
|
||||
- `open_notifications_menu`
|
||||
- `open_creator_from_home`
|
||||
- `open_profile_from_avatar_menu`
|
||||
- `open_profile_answers_tab`
|
||||
- `open_profile_articles_tab`
|
||||
- `open_security_settings_from_avatar_menu`
|
||||
|
||||
## Confirmed Alias Conflicts
|
||||
|
||||
These aliases currently resolve to more than one target and must not be guessed:
|
||||
|
||||
| Alias | Conflicting targets |
|
||||
| --- | --- |
|
||||
| `关注分栏` | `home_feed_following_tab`, `profile_following_tab` |
|
||||
| `回答排序菜单` | `answer_sort_menu`, `question_sort_menu` |
|
||||
|
||||
## Preferred Disambiguation Wording
|
||||
|
||||
When the user uses an ambiguous alias, ask for the missing context directly:
|
||||
|
||||
- `你说的“关注分栏”是首页关注流,还是个人主页里的关注分栏?`
|
||||
- `你说的“回答排序菜单”是问题页的排序菜单,还是回答列表的排序菜单?`
|
||||
|
||||
## Practical Routing Rule
|
||||
|
||||
Prefer the most explicit phrase in this order:
|
||||
|
||||
1. exact target name
|
||||
2. exact alias
|
||||
3. explicit page + area combination
|
||||
4. generic area noun only
|
||||
|
||||
If step 3 or 4 still matches more than one target, ask before acting.
|
||||
|
||||
Reference in New Issue
Block a user