Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

better-vibe

Use when designing, reviewing, or implementing full-stack application structure and engineering boundaries. Especially use when frontend pages are becoming overloaded, presentation code is mixing with backend concerns, backend services are growing into large coupled modules, or the system needs clearer separation between UI, business logic, persistence, and cross-layer responsibilities.

Exécuter dans Manus

Aperçu

Commande d'installation

npx skills add https://github.com/WncFht/agent-basic-skill --skill better-vibe

Copiez et collez cette commande dans Claude Code pour installer le skill

Source

WncFht/agent-basic-skill

Étoiles14

Forks1

Mis à jour10 avril 2026 à 14:45

Explorateur de fichiers

4 fichiers

SKILL.md

readonly

name	better-vibe
description	Use when designing, reviewing, or implementing full-stack application structure and engineering boundaries. Especially use when frontend pages are becoming overloaded, presentation code is mixing with backend concerns, backend services are growing into large coupled modules, or the system needs clearer separation between UI, business logic, persistence, and cross-layer responsibilities.

Better Vibe

Overview

这是一个全栈工程护栏 skill。

它不负责讲具体框架 API，重点是约束：

前端页面职责
后端分层边界
前后端耦合方式
模块拆分与可维护性

Trigger Signals

当请求或上下文出现以下信号时，优先使用本 skill：

单个前端页面越来越重，开始堆逻辑、堆状态、堆展示
展示层开始混入后端能力、业务编排、复杂数据处理
后端 controller / service / handler 变得过大、过杂、过耦合
前后端边界混乱，职责分配不清
项目虽然能跑，但维护成本明显升高
用户明确要求从全栈工程角度约束架构和职责

Core Rule

先判断问题属于哪一层：

前端页面职责问题
后端分层问题
前后端边界问题

再按需读取对应 reference，不要一次性展开全部细节。

Default Working Rules

先识别当前问题的主要耦合点。
判断问题主要落在前端、后端，还是边界层。
优先做职责拆分，而不是继续往现有大文件或大模块里堆代码。
优先保证层与层之间职责清楚，而不是局部代码“暂时能跑”。
默认追求可维护、可替换、可测试的结构。
如果当前项目存在 .trellis/spec/backend/ 或 .trellis/spec/guides/，边界与分层规范优先参考这些项目内文档；本 skill 自带 references 只做补充。

Read References When Needed

需要判断前端页面职责和展示层边界时，读 references\frontend-boundaries.md
需要判断后端分层、服务边界和副作用隔离时，读 references\backend-boundaries.md
需要判断前后端如何解耦、如何分配职责时，读 references\fullstack-boundaries.md

Hard Constraints

不把前端页面当成业务编排中心
不把后端 service 当成万能垃圾桶
不把数据库结构直接暴露成前端接口结构
不让前后端为了省事互相吞掉对方职责
不因为“当前能跑”就接受明显会继续膨胀的结构
不与当前项目内的 .trellis/spec/backend/*、.trellis/spec/guides/* 长期维持两套平行边界规范

Red Flags

单个页面文件越来越长，而且同时在做展示、状态、数据、流程控制
controller / handler 里直接塞大量业务判断和数据处理
service 里同时做权限、事务、缓存、第三方调用、返回组装
前端为了拿到页面数据，不得不依赖后端返回高度展示化结构
改一个需求时，前后端两边都要跟着大改

Plus depuis ce dépôt

même dépôt

better-gpt

WncFht/agent-basic-skill

Use as the workspace-level entry skill for this repository when responses should follow BetterGPT defaults. This skill routes by default to BetterLanguage for language shaping, then applies task-specific enhancements only when needed, such as BetterFrontend for frontend presentation work, BetterVibe for full-stack engineering boundary and maintainability guidance, BetterTrellis for Trellis workflow, Codex soft integration, initialization, spec, task, and hooks-related guidance, and BetterSubagents for subagent delegation, orchestration, wait handling, and takeover guardrails. Use when a single main entry skill should coordinate default loading order and on-demand sub-skill activation.

2026-04-1114

pdf

WncFht/agent-basic-skill

Use when tasks involve reading, creating, or reviewing PDF files where rendering and layout matter; prefer MinerU API first for parsing/extraction, then use visual checks with Poppler and Python tools such as `reportlab`, `pdfplumber`, and `pypdf` for generation or fallback extraction.

2026-04-1014

better-frontend

WncFht/agent-basic-skill

Use when generating, revising, polishing, or reviewing frontend UI, landing pages, dashboards, app screens, marketing pages, or other presentation-layer output that should look like a production-ready product instead of a demo, draft, wireframe, showcase, or developer-facing mockup. Especially use when the request mentions removing AI-like UI, avoiding demo feel, preventing TODO or note text, hiding reasoning or design commentary from users, eliminating placeholder explanations, or making the final interface feel shippable, real, and user-facing.

2026-04-1014

better-language

WncFht/agent-basic-skill

Use when GPT-5.4 style answers need to be rewritten into concise, natural Chinese with minimal filler, no internet slang or habitual phrasing, and a strict two-part structure that users can scan top-to-bottom at a glance. Especially use when the output should preserve two-part reasoning and solution flow without always printing rigid section titles, allow light line breaks for readability, remove translation-like Chinese, and switch to terminal-friendly rendering when the current surface is CLI or shell rather than an app-style chat surface.

2026-04-1014

better-subagents

WncFht/agent-basic-skill

Use when the task involves subagent selection, delegation strategy, parallel execution, wait and timeout handling, fallback takeover, or how to correctly use the project's local agents together with repository skills and MCP tools. Especially use when the user asks how to orchestrate explorer, worker, reviewer, docs-researcher, code-mapper, frontend-developer, browser-debugger, refactoring-specialist, or other local subagents, or when the main agent needs stronger delegation guardrails.

2026-04-1014

better-trellis

WncFht/agent-basic-skill

Use when working with Trellis in Codex, especially for soft integration, project initialization, workflow entry, spec and task organization, hooks, generated command structure, or reducing the need to remember Trellis commands manually. Use when the request mentions Trellis init, Codex integration, workflow, spec, task, workspace logs, hooks, update, onboarding, or agent command mapping.

2026-04-1014

Source

WncFht

WncFht/agent-basic-skill

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Commande d'installation

Téléchargement

Exécuter dans Manus

Utile pourSOC

Développeurs de logicielsProfessions informatiques et mathématiques15-1252L4

name	better-vibe
description	Use when designing, reviewing, or implementing full-stack application structure and engineering boundaries. Especially use when frontend pages are becoming overloaded, presentation code is mixing with backend concerns, backend services are growing into large coupled modules, or the system needs clearer separation between UI, business logic, persistence, and cross-layer responsibilities.

Better Vibe

Overview

这是一个全栈工程护栏 skill。

它不负责讲具体框架 API，重点是约束：

前端页面职责
后端分层边界
前后端耦合方式
模块拆分与可维护性

Trigger Signals

当请求或上下文出现以下信号时，优先使用本 skill：

单个前端页面越来越重，开始堆逻辑、堆状态、堆展示
展示层开始混入后端能力、业务编排、复杂数据处理
后端 controller / service / handler 变得过大、过杂、过耦合
前后端边界混乱，职责分配不清
项目虽然能跑，但维护成本明显升高
用户明确要求从全栈工程角度约束架构和职责

Core Rule

先判断问题属于哪一层：

前端页面职责问题
后端分层问题
前后端边界问题

再按需读取对应 reference，不要一次性展开全部细节。

Default Working Rules

先识别当前问题的主要耦合点。
判断问题主要落在前端、后端，还是边界层。
优先做职责拆分，而不是继续往现有大文件或大模块里堆代码。
优先保证层与层之间职责清楚，而不是局部代码“暂时能跑”。
默认追求可维护、可替换、可测试的结构。
如果当前项目存在 .trellis/spec/backend/ 或 .trellis/spec/guides/，边界与分层规范优先参考这些项目内文档；本 skill 自带 references 只做补充。

Read References When Needed

需要判断前端页面职责和展示层边界时，读 references\frontend-boundaries.md
需要判断后端分层、服务边界和副作用隔离时，读 references\backend-boundaries.md
需要判断前后端如何解耦、如何分配职责时，读 references\fullstack-boundaries.md

Hard Constraints

不把前端页面当成业务编排中心
不把后端 service 当成万能垃圾桶
不把数据库结构直接暴露成前端接口结构
不让前后端为了省事互相吞掉对方职责
不因为“当前能跑”就接受明显会继续膨胀的结构
不与当前项目内的 .trellis/spec/backend/*、.trellis/spec/guides/* 长期维持两套平行边界规范

Red Flags

单个页面文件越来越长，而且同时在做展示、状态、数据、流程控制
controller / handler 里直接塞大量业务判断和数据处理
service 里同时做权限、事务、缓存、第三方调用、返回组装
前端为了拿到页面数据，不得不依赖后端返回高度展示化结构
改一个需求时，前后端两边都要跟着大改