Menu
Use this when setting up a fresh new project.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Best practices for AI-driven English-to-Chinese translation. This skill should be used when the user asks to "translate to Chinese", "update the Chinese translation", "improve Chinese translation", "fix translation quality", "review Chinese translation", or when translating any English text into Chinese. Also applies when polishing an existing Chinese translation of English content.
This skill should be used when sending images, files, or notifications back to the user via messaging platforms (Discord, Feishu, Telegram, etc.) through cc-connect. TRIGGER when agent generates a plot/chart/screenshot and wants to show the user; agent creates a report/PDF/file the user should receive; agent needs to proactively notify the user (e.g. task completed, alert, reminder); user asks to "send image", "show me the chart", "notify me", "send the file", "send to Telegram", "show plot in Discord".
Browser automation CLI for AI agents. Use when needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. TRIGGER when user requests to "open a website", "fill out a form", "click a button", "take a screenshot", "debug this in browser", "scrape data from a page", "test this web app", "login to a site", "frontend UI/UX aesthetics", "automate browser actions", or any task requiring programmatic web interaction.
Review common AI slops of defensive programming patterns, avoid silent errors. TRIGGER when reviewing code for defensive anti-patterns, writing fail-fast code, or auditing error handling quality.
Guide for writing ast-grep rules to perform structural code search and analysis. This skill should be used when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search, or when a simple grep/glob search is insufficient for structural code pattern matching.
This skill should be used when the user asks about "code complexity", "cyclomatic complexity", "cognitive complexity", "code metrics", "maintainability index", "code coverage", or when measuring code quality quantitatively. Provides metrics thresholds and measurement techniques.
| name | setup-fresh-project |
| description | Use this when setting up a fresh new project. |
Use this skill when you are starting to write code in a fresh project.
git init..gitignore suitable for tech stack of choices (e.g. __pycache__ for Python, node_modules for Node)..stylua.toml for Lua, pyproject.toml + Ruff for Python). Default to 4 spaces for tab.stylua, npm, uv). If not, explicitly ask the user to install.Ask user for tech stack choices. Offer default choices:
Prefer uv (with venv) and ruff.
If you are using venv, to prevent LSP errors about 'package not found', create pyrightconfig.json with content:
{
"venvPath": ".",
"venv": ".venv"
}
Prefer biome and npm (or bun).
Prefer stylua.
If the Lua project is used as a NeoVim configuration or plugin:
Create a .luarc.json with content:
{
"runtime.version": "LuaJIT",
"runtime.path": [
"lua/?.lua",
"lua/?/init.lua"
],
"diagnostics.globals": ["vim"],
"workspace.checkThirdParty": false,
"workspace.library": [
"$VIMRUNTIME"
]
}
Prefer clang, cmake and clang-format.
Make sure to use cmake -B build -DCMAKE_EXPORT_COMPILE_COMMANDS=ON when build (or add set(CMAKE_EXPORT_COMPILE_COMMANDS ON) to CMakeLists.txt). This will create build/compile_commands.json, for clangd to not reporting false positive errors about include header missing.
Follow industry best pratice of project folder structure most suitable the tech stack.
e.g.:
src/, tests/, dist/ for Python & PyTest project.src/, include/, build/ for C++ & CMake project.lua/ for NeoVim Lua plugin project.A .gitignore and README.md is always required for all projects.
Main documentation resides in README.md. With a simple and clear introduction on how to use this project, including but not limited to the following perspectives:
README.md must be presented in a clear, structured markdown format. No placeholders.
README.md focus on big-picture. Optionally create .md under docs/ for more detailed documentation and refer them in README.md.
If this is to be a public project (potentially upload to github), not for personal use:
/home/bate/project) in README.md and other documents.README.md and other documents (e.g. [Screenshot](screenshot.png) but actually no such file).