Menu
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/archibate/dotfiles-opencode --skill setup-fresh-projectThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Based on SOC occupation classification
Showing SKILL.md
| 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 ).
bunPrefer 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).