Initialize new software projects with TypeScript, linting, formatting, and Git setup.
npx skills add https://github.com/SpaceZephyr/myskill --skill project-init-spacezephyr
Please help me install this Agent Skill. Skill: project-init Source: https://github.com/SpaceZephyr/myskill/tree/main/project-init Command: npx skills add https://github.com/SpaceZephyr/myskill --skill project-init-spacezephyr
This Skill helps you turn a new project idea into a runnable codebase by guiding requirements alignment, stack selection, scaffolding, and development standards.
Describe your new project goals, preferred technologies, target platform, and deployment style, and ask this Skill to help you design and initialize the project setup.
High-intent search queries and answers about installing and using this skill.
To initialize a new TypeScript project, you need to scaffold the folder structure, configure the build tooling, and set up ESLint and Prettier for linting and formatting. This establishes a working development baseline with Git initialized.
Scaffolding a runnable codebase involves guiding requirements alignment, selecting a practical tech stack for your platform targets, and configuring the starter setup. This process ensures a clear technical direction and a verified runnable development environment.
Yes, project scaffolding applies to web apps, mobile apps, CLI tools, and desktop applications. It helps clarify product type and MVP scope while recommending practical choices for frontend, backend, and database layers.
Setting up development standards requires configuring TypeScript, ESLint, and Prettier during the initial project setup. This establishes coding conventions, project guidance, and a README foundation for future work.
Defining deployment needs, preferred technologies, and platform targets is required before tech stack recommendation. Clarifying these requirements discovery details ensures practical choices for frontend, backend, database, and package management.
Project initialization requires requirements alignment to clarify product type, MVP scope, and platform targets. This ensures the selected tech stack and folder structure planning match your deployment needs and working development baseline.
Pratikkadam254Define lean MVPs with 1-3 core features and a two-week sprint plan.
Yanick-mjGenerate test suites and coverage reports for changed code files.
NASA-AMMOSAutomate vulnerability scanning for Docker images and package dependencies with Grype.
TMHSDigitalScaffold an Expo React Native project with TypeScript and file-based routing.
