Agent skill

Project Bootstrap

A skill your agent uses when launching a new project, initializing a repository, or building a codebase from the ground up - addresses directory structure, tooling configuration, linting, testing…

MITAuto-check: notesDevelopment

Install Project Bootstrap

skills CLI

$ npx skills add NoobyGains/godmode --skill project-bootstrap -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install NoobyGains/godmode project-bootstrap --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/NoobyGains/godmode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/project-bootstrap .claude/skills/project-bootstrap && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "project-bootstrap" agent skill from https://github.com/NoobyGains/godmode/tree/master/skills/project-bootstrap into .claude/skills/project-bootstrap/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-bootstrap", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/NoobyGains/godmode/tree/master/skills/project-bootstrap

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add NoobyGains/godmode --skill project-bootstrap -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install NoobyGains/godmode project-bootstrap --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NoobyGains/godmode.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/project-bootstrap .agents/skills/project-bootstrap && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "project-bootstrap" agent skill from https://github.com/NoobyGains/godmode/tree/master/skills/project-bootstrap into .agents/skills/project-bootstrap/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-bootstrap", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add NoobyGains/godmode --skill project-bootstrap -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install NoobyGains/godmode project-bootstrap --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NoobyGains/godmode.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/project-bootstrap .cursor/skills/project-bootstrap && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "project-bootstrap" agent skill from https://github.com/NoobyGains/godmode/tree/master/skills/project-bootstrap into .cursor/skills/project-bootstrap/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-bootstrap", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/NoobyGains/godmode.git --path skills/project-bootstrap

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add NoobyGains/godmode --skill project-bootstrap -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install NoobyGains/godmode project-bootstrap --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NoobyGains/godmode.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/project-bootstrap .gemini/skills/project-bootstrap && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "project-bootstrap" agent skill from https://github.com/NoobyGains/godmode/tree/master/skills/project-bootstrap into .gemini/skills/project-bootstrap/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-bootstrap", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install NoobyGains/godmode project-bootstrap

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add NoobyGains/godmode --skill project-bootstrap -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/NoobyGains/godmode.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/project-bootstrap .github/skills/project-bootstrap && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "project-bootstrap" agent skill from https://github.com/NoobyGains/godmode/tree/master/skills/project-bootstrap into .github/skills/project-bootstrap/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-bootstrap", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add NoobyGains/godmode --skill project-bootstrap -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install NoobyGains/godmode project-bootstrap --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NoobyGains/godmode.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/project-bootstrap .opencode/skills/project-bootstrap && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "project-bootstrap" agent skill from https://github.com/NoobyGains/godmode/tree/master/skills/project-bootstrap into .opencode/skills/project-bootstrap/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-bootstrap", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: project-bootstrap
GitHub stars: 107
Token cost: ~1.9k tokens
SKILL.md length: 581 words
Files: 2
Skills in repo: 34
Repo updated: Mar 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when launching a new project, initializing a repository, or building a codebase from the ground up - addresses directory structure, tooling configuration, linting, testing…

Works in 5 steps: Version Control Hygiene → Static Analysis and Formatting → Test Infrastructure → …
Launching a new project
SKILL.md covers Overview, The Prime Directive, When to Use and The Entry Protocol, plus 8 more sections
Calls go and cargo

What it does

Project Bootstrap is an agent skill from NoobyGains/godmode. Use when launching a new project, initializing a repository, or building a codebase from the ground up - addresses directory structure, tooling configuration, linting, testing infrastructure, CI/CD pipelines, and version control setup

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `templates.md`).

It sits in Development, covering Linting and formatting, Git workflow and CI/CD. It works with TypeScript. The repository describes itself as: The AI development framework that thinks before it builds. 36 composable skills for Claude Code, Cursor, Codex, and OpenCode. The licence is MIT.

When your agent uses it

Launching a new project
Initializing a repository
Building a codebase from the ground up - addresses directory structure
Tooling configuration

Example prompts

“/project-bootstrap”

Requirements

Python 3

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Version Control Hygiene
Static Analysis and Formatting
Test Infrastructure
Type Safety
Continuous Integration Minimum

What it can do on your machine

Read from SKILL.md and the folder at commit 441103a. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- go
- cargo
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Project Bootstrap loads about 1.9k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 581 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~63
When it runs · the whole SKILL.md, loaded when a task matches: ~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:93

- `.env`, `.env.local`, `.env.*.local` (secrets and credentials)

NoteMentions a .env fileSKILL.md:196

The .gitignore can wait" | One committed .env file means leaked credentials. Configure it first. |

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NoobyGains/godmode at commit 441103a, republished under its MIT licence (© NoobyGains). 581 words, ~1,905 tokens.

Download SKILL.mdSave it as .claude/skills/project-bootstrap/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: project-bootstrap
description: Use when launching a new project, initializing a repository, or building a codebase from the ground up - addresses directory structure, tooling configuration, linting, testing infrastructure, CI/CD pipelines, and version control setup

Project Bootstrap

Overview

A properly initialized project prevents 80% of future structural headaches.

Core principle: Invest 30 minutes in setup now, or spend 30 hours unwinding structural debt later.

No exceptions. No workarounds. No shortcuts.

The Prime Directive

NO FEATURE CODE BEFORE PROJECT STRUCTURE IS ESTABLISHED

If the project lacks linting, formatting, testing infrastructure, and version control hygiene, address those gaps before writing any business logic.

When to Use

Mandatory when:

Creating a new project from nothing
"Just get something running" (especially then)
Building a prototype that could evolve into production
Setting up a shared repository for a team

Also applicable when:

Inheriting a project with no structural foundation
Retrofitting test infrastructure into untested code
Introducing CI/CD for the first time

The Entry Protocol

BEFORE writing any feature code:

1. STRUCTURE: Is the directory layout established?
2. TOOLING: Are linter, formatter, and type checker wired up?
3. TESTING: Is the test runner configured with a passing placeholder?
4. VERSION CONTROL: Are .gitignore, branch conventions, and hooks set up?
5. DEPENDENCIES: Is the package manager initialized with a committed lockfile?
6. AUTOMATION: Does at minimum a lint + test pipeline exist?

If any answer is NO: fix it first.

Project Classification

dot

digraph project_class {
    start [label="What is being\nbuilt?", shape=diamond];
    web [label="Web\napplication?", shape=diamond];
    api [label="API /\nbackend?", shape=diamond];
    cli [label="CLI tool?", shape=diamond];
    lib [label="Library /\npackage?", shape=diamond];

    web_tpl [label="Web App\nBlueprint", shape=box, style=filled, fillcolor="#ccffcc"];
    api_tpl [label="API\nBlueprint", shape=box, style=filled, fillcolor="#ccccff"];
    cli_tpl [label="CLI\nBlueprint", shape=box, style=filled, fillcolor="#ffffcc"];
    lib_tpl [label="Library\nBlueprint", shape=box, style=filled, fillcolor="#ffccff"];
    general [label="General\nBlueprint", shape=box, style=filled, fillcolor="#ffcccc"];

    start -> web [label="assess"];
    web -> web_tpl [label="yes"];
    web -> api [label="no"];
    api -> api_tpl [label="yes"];
    api -> cli [label="no"];
    cli -> cli_tpl [label="yes"];
    cli -> lib [label="no"];
    lib -> lib_tpl [label="yes"];
    lib -> general [label="no"];
}

Consult templates.md for detailed setup checklists per project classification.

Universal Foundation (All Projects)

1. Version Control Hygiene

.gitignore          # Language-specific + universal exclusions
.gitattributes      # Line ending normalization, binary file handling

Mandatory .gitignore entries:

node_modules/, venv/, __pycache__/, target/ (dependency directories)
.env, .env.local, .env.*.local (secrets and credentials)
*.log (log files)
.DS_Store, Thumbs.db (OS artifacts)
IDE directories: .idea/, .vscode/ (unless sharing settings deliberately)
Build output: dist/, build/, out/

2. Static Analysis and Formatting

Language	Linter	Formatter
TypeScript/JavaScript	ESLint	Prettier
Python	Ruff (lint + format)	Ruff
Go	golangci-lint	gofmt (built-in)
Rust	clippy	rustfmt (built-in)
Ruby	RuboCop	RuboCop

Install on day one. Adopting a linter after 10,000 lines means triaging hundreds of violations on your first run.

3. Test Infrastructure

Language	Framework	Runner
TypeScript/JavaScript	Vitest or Jest	Built-in
Python	pytest	Built-in
Go	testing (stdlib)	`go test`
Rust	built-in test harness	`cargo test`
Ruby	RSpec or Minitest	Built-in

Write one passing test immediately. This confirms the test pipeline functions before you actually need it.

4. Type Safety

Language	Requirement
TypeScript	`strict: true` in tsconfig.json. Non-negotiable.
Python	Type annotations + mypy or pyright
JavaScript	Consider TypeScript. If not, at minimum use JSDoc type annotations.

5. Continuous Integration Minimum

Every project must have at minimum:

yaml

# Minimum CI pipeline (GitHub Actions example)
on: [push, pull_request]
jobs:
  check:
    steps:
      - lint
      - type-check
      - test

If it does not execute in CI, it will not be maintained.

Directory Structure Principles

Organize by feature, not by file type (see godmode:system-design).

Every project requires:

project-root/
  src/              # Source code (or lib/, app/ per convention)
  tests/            # Test files (or co-located alongside source)
  docs/             # Documentation (when applicable)
  scripts/          # Build, deploy, and utility scripts
  .gitignore
  README.md         # Purpose, installation, how to run
  <config files>    # Linter, formatter, CI, package manager

Co-located tests vs separate directory:

Co-located (payment.ts + payment.test.ts): Easier to maintain, preferred default
Separate (tests/): When tests require shared fixtures or team convention mandates it

Show full SKILL.md (229 more words)Show less

Dependency Governance

BEFORE adding any dependency:

1. Is it genuinely necessary? Could you write it in under 50 lines?
2. Is it actively maintained?
3. How many transitive dependencies does it introduce?
4. Does it carry known vulnerabilities?

When uncertain, write the code yourself.

Always:

Commit lockfiles (package-lock.json, poetry.lock, Cargo.lock)
Pin major versions, permit patch-level updates
Execute security audit in CI

Cognitive Traps

Rationalization	Truth
"It is just a prototype"	Prototypes graduate to production. Initialize properly.
"I will add linting later"	After 10,000 lines you will face hundreds of violations. Now is always easier.
"Tests decelerate initial development"	Test setup takes 5 minutes. Hunting bugs without tests takes hours.
"CI is excessive for this"	CI catches what you forget. Wire it up on day one.
"I will organize the files later"	You will not. Directory structure is harder to change than code.
"The .gitignore can wait"	One committed .env file means leaked credentials. Configure it first.

Guardrails -- HALT and Set Up

Writing features without a linter configured
No .gitignore in the repository
No test framework installed
Secrets committed to version history (even once, even if deleted -- they persist in git history)
No README explaining how to run the project
Build artifacts checked into git
No CI pipeline
any types everywhere (TypeScript)

Every item on this list means: halt feature work. Fix the foundation first.

Integration

Complementary skills:

godmode:system-design -- Directory structure and technology selection
godmode:quality-enforcement -- Quality gates wired into CI from the start
godmode:security-protocol -- Secrets management and .gitignore discipline
godmode:ux-patterns -- Design system initialization for UI projects

The Bottom Line

30 minutes of setup now > 30 hours of structural debt later

Linter. Formatter. Tests. CI. .gitignore. README. Before the first feature. Every single time.

Files

SKILL.md and 1 other file in skills/project-bootstrap of NoobyGains/godmode.

SKILL.md
templates.md

Open the folder on GitHubat commit 441103a

Compare with similar skills

Project Bootstrap next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Project Bootstrap compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Project Bootstrap this skillNoobyGains/godmode	107	—	~1.9k	Automated safety check: Notes	MIT	7 mo ago
Project Initathola/claude-night-market	342	—	~1.2k	Automated safety check: Pass	MIT	2 days ago
Workflow Setupathola/claude-night-market	342	—	~1.4k	Automated safety check: Pass	MIT	2 days ago
Configuration GeneratorArabelaTso/Skills-4-SE	253	—	~2.8k	Automated safety check: Notes	Apache-2.0	1 mo ago
Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop	5.3k	1 repos	~2.2k	Automated safety check: Pass	MIT	28 days ago
Babysit PR To Pass CIsgl-project/sglang	37k	2 repos	~3k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Project Init
athola/claude-night-market
Scaffolds new projects with git, CI/CD workflows, pre-commit hooks, and build config.
342 GitHub stars~1.2k tokensUpdated 2 days ago
DevelopmentAuto-check passed
Workflow Setup
athola/claude-night-market
Configures GitHub Actions CI/CD workflows for testing, linting, and deployment.
342 GitHub stars~1.4k tokensUpdated 2 days ago
DevOps & CloudAuto-check passed
Configuration Generator
ArabelaTso/Skills-4-SE
Generate configuration files for applications, services, and infrastructure.
253 GitHub stars~2.8k tokensUpdated 1 mo ago
DevOps & CloudAuto-check: notes
Install Anti-Slop Oxlint Rules
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
5.3k GitHub starsUsed in 1 repo~2.2k tokens
DevelopmentAuto-check passed
Babysit PR To Pass CI
sgl-project/sglang
Start and persistently pursue a goal to babysit an SGLang pull request until selected GitHub Actions workflows pass on the latest PR head.
37k GitHub starsUsed in 2 repos~3k tokens
DevelopmentAuto-check passed
Kedro Babysit
kedro-org/kedro
Run Kedro's local lint / format / type-check / tests on changed files (uses the project's pre-commit hooks, ruff, mypy, pytest, lint-imports, detect-secrets, Make targets — in the right venv), or…
11k GitHub stars~4k tokensUpdated yesterday
DevelopmentAuto-check passed

Questions about Project Bootstrap

What does Project Bootstrap do?

A skill your agent uses when launching a new project, initializing a repository, or building a codebase from the ground up - addresses directory structure, tooling configuration, linting, testing…. Project Bootstrap is an agent skill from NoobyGains/godmode.

When should I use Project Bootstrap?

Project Bootstrap fits situations like: launching a new project; initializing a repository; building a codebase from the ground up - addresses directory structure; tooling configuration.

How do I install Project Bootstrap in Claude Code?

Run `npx skills add NoobyGains/godmode --skill project-bootstrap -a claude-code`. Or copy the skill folder (skills/project-bootstrap in NoobyGains/godmode) into .claude/skills/project-bootstrap in your project. Claude Code loads it when a task matches its description.

How do I install Project Bootstrap in Codex?

Run `npx skills add NoobyGains/godmode --skill project-bootstrap -a codex`. Or copy the skill folder (skills/project-bootstrap in NoobyGains/godmode) into .agents/skills/project-bootstrap in your project. Codex loads it when a task matches its description.

Can I use Project Bootstrap in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NoobyGains/godmode --skill project-bootstrap -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/project-bootstrap, .gemini/skills/project-bootstrap, .github/skills/project-bootstrap and .opencode/skills/project-bootstrap in your project.

What does Project Bootstrap need to run?

Going by SKILL.md and its folder, Project Bootstrap needs the command-line tools its instructions call (go and cargo). Our summary lists: Python 3.

Does Project Bootstrap access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Project Bootstrap safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Project Bootstrap use?

Project Bootstrap is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Project Bootstrap use?

About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Project Bootstrap?

Skills that share tags, products or a category with Project Bootstrap: Project Init (athola/claude-night-market, 342 stars), Workflow Setup (athola/claude-night-market, 342 stars), Configuration Generator (ArabelaTso/Skills-4-SE, 253 stars) and Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Project Bootstrap?

NoobyGains (a GitHub user) maintains it in NoobyGains/godmode, which has 107 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on March 9, 2026.

Source: NoobyGains/godmode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Project Bootstrap

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Project Bootstrap

Overview

The Prime Directive

When to Use

The Entry Protocol

Project Classification

Universal Foundation (All Projects)

1. Version Control Hygiene

2. Static Analysis and Formatting

3. Test Infrastructure

4. Type Safety

5. Continuous Integration Minimum

Directory Structure Principles

Dependency Governance

Cognitive Traps

Guardrails -- HALT and Set Up

Integration

The Bottom Line

Files

Compare with similar skills

Similar skills

More from NoobyGains/godmode

Related

Questions about Project Bootstrap