frontend-integration
Routes Nexent frontend App Router work, service clients, typed API contracts, streaming chat, i18n, and frontend build checks.
- License 许可
- MIT
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- frontend-integration
- license
- MIT
- metadata
- { "disco-role": "operating" }
- description
- Routes Nexent frontend App Router work, service clients, typed API contracts, streaming chat, i18n, and frontend build checks.
- disable-model-invocation
- true
02 资源文件 5
- 参考文档references/api-contracts.md6.0 KB
- 参考文档references/frontend-architecture.md5.9 KB
- 参考文档references/streaming-and-chat.md8.9 KB
- 参考文档references/troubleshooting.md5.0 KB
- 脚本scripts/extract_frontend_api_calls.py6.2 KB
03 SKILL.md 正文
Frontend Integration
Use this sub-skill for Nexent frontend tasks that touch the Next.js App Router, service clients, typed response contracts, streaming chat, localization, or frontend build checks.
Route here when the task is about
frontend/app/[locale]/pages and layoutsfrontend/components/,frontend/features/,frontend/hooks/,frontend/stores/,frontend/services/,frontend/types/, andfrontend/const/- chat streaming, assistant-ui, dictation, attachments, resume/replay, or share rendering
- locale routing, translation JSON, or base-path/proxy behavior
npm run check-all,npm run type-check,npm run lint, ornpm run build
Read first
Bundled helper
scripts/extract_frontend_api_calls.py --repo-root <repo-root>- Add
--jsonfor machine-readable output. - Use it to inventory
API_ENDPOINTScall sites before changing client contracts.
- Add
Keep these layers in sync
When backend payloads or route behavior change, update the frontend in this order:
frontend/services/api.ts- the affected
frontend/services/*.tsclient mapper - the matching
frontend/types/*.ts - the consuming page, hook, store, or component
- any chat-stream mapping in
frontend/app/[locale]/chat/streaming/orfrontend/app/[locale]/newchat/adapter/
Route elsewhere
- Backend app/service/database internals ->
../backend-services-api/SKILL.md - SDK runtime, model, tool, or observer semantics ->
../sdk-agent-runtime/SKILL.md - Deployment scripts, env templates, SQL/init sync, or rollout behavior ->
../deployment-operations/SKILL.md
Main frontend surfaces
- Chat and streaming:
app/[locale]/chat/,app/[locale]/newchat/ - Agent/model/knowledge/memory setup:
app/[locale]/agents/,models/,knowledges/,memory/ - Repository and marketplace:
agent-space/,skill-space/,mcp-space/,market/ - Shared runtime:
components/providers/,hooks/,services/,stores/,types/,lib/,public/locales/
04 同仓库更多 Skills
passnet-triton-opt
Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block/grid/warp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.
passnet-solve
END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.
passnet-skill
PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under ./pass_dir/, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.
passnet-pattern-fusion
Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()/replacement_args()/replacement_func() files, when a pass "failed to match", or when deciding how to fuse multiple kernels/ops.
passnet-orchestrate
Round/batch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep/revert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.
passnet-feedback
Fast, deterministic feedback for PassNet work: pre-flight pattern/match verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).