-
Notifications
You must be signed in to change notification settings - Fork 4
Tracing dashboard redesign + robust project-memory capacity handling #126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
46e75b8
feat: MCP skill bridge, agent guardrails, and session UX fixes
elkaix 7315291
fix(tui): render diff context lines in normal text color
elkaix 944d38e
Redesign tracing dashboard with Usage page and polish
elkaix 3e8113a
Rank command-name matches above alias matches in slash completer
elkaix 32f860d
Polish dashboard with blue accent and richer Usage page
elkaix 0866cfe
chore(deps): bump react to 19.2.7 in vis and web
elkaix 9ba42df
Make Daily Usage chart fill the card width
elkaix b69177e
fix(memory): legible capacity errors, list action, and full-store edu…
elkaix File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,43 @@ | ||
| --- | ||
| name: designer-skill | ||
| description: Prescriptive frontend design guidance via the designer-skill MCP server. Use when the user asks to use designer-skill, improve UI/UX, run the anti-slop ship gate, apply a design system, or enhance pages/components with MCP-backed design references — especially for Pythinker docs and marketing surfaces with DESIGN.md/PRODUCT.md. | ||
| --- | ||
|
|
||
| # designer-skill (MCP) | ||
|
|
||
| `designer-skill` is **not** a filesystem workflow skill. It is delivered by the connected **designer-skill MCP server**. After reading this stub, call the MCP tools below — do **not** call `ReadSkill` again for the same name. | ||
|
|
||
| ## Required MCP tools | ||
|
|
||
| Call these by their registered tool keys (`mcp__designer-skill__<tool>`): | ||
|
|
||
| | Step | Tool | Purpose | | ||
| | --- | --- | --- | | ||
| | 1 | `get_design_system` | Session preflight, precedence rules, routing map, ship-gate overview | | ||
| | 2 | `get_reference` | Load the specific reference file the task needs | | ||
| | 3 | `dispatch_intent` | Route ambiguous design requests to the right reference/workflow | | ||
| | 4 | `apply_designer` | Apply prescriptive design moves to the scoped surface | | ||
| | 5 | `anti_slop_checklist` | Mandatory ship gate before declaring frontend work done | | ||
|
|
||
| If a tool is missing, check `/mcp` — the server may still be connecting. | ||
|
|
||
| ## Session preflight | ||
|
|
||
| Before editing UI: | ||
|
|
||
| 1. Read project design sources when present (`DESIGN.md`, `PRODUCT.md`, or equivalent). | ||
| 2. Call `get_design_system` first. | ||
| 3. Pull only the references the scoped surface needs via `get_reference`. | ||
| 4. Implement changes; run `anti_slop_checklist` before finishing. | ||
|
|
||
| ## Common aliases | ||
|
|
||
| These names refer to the same MCP integration — always use MCP tools, not `ReadSkill`: | ||
|
|
||
| - `designer-skill` | ||
| - `designer-skill:designer-skill` (plugin-style slash autocomplete) | ||
| - "use designer-skill mcp" / "designer mcp" | ||
|
|
||
| ## When MCP is unavailable | ||
|
|
||
| If `/mcp` shows designer-skill disconnected, run `pythinker mcp` to configure/auth it. Do not substitute ad-hoc design advice for the MCP workflow when the user explicitly requested designer-skill. |
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Log best-effort cleanup failures instead of fully suppressing them.
At Line 1206, exceptions from
cleanup_session_scratch(...)are swallowed without any trace. Keep it best-effort, but log failures so repeated scratch-cleanup regressions are diagnosable.Proposed fix
As per coding guidelines, exception handlers that silently swallow errors should be logged or re-raised.
🤖 Prompt for AI Agents
Source: Coding guidelines