stacks

Detect active project stacks and apply ecosystem-specific conventions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mrsknetwork/nemodev --skill stacks-mrsknetwork
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stacks
Source: https://github.com/mrsknetwork/nemodev/tree/main/skills/stacks
Command: npx skills add https://github.com/mrsknetwork/nemodev --skill stacks-mrsknetwork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stack-agnostic conventions and project scaffolding rules ensure that code adheres to ecosystem idioms across Python/FastAPI, Node.js/TypeScript, Next.js, and Go, reducing onboarding friction and inconsistencies.

Core Features & Use Cases

  • Stack detection by scanning for signature files (pyproject.toml, package.json, go.mod, next.config.*) to determine the active stack.
  • Reference loading per stack via dedicated guidance (references/python-fastapi.md, references/node-typescript.md, references/nextjs.md, references/go.md).
  • Universal conventions (env vars, lockfiles, README, structured logging) applied at the repository root.
  • Handoff flow to the plan or generate skills after conventions are established for a new project or repository update.

Quick Start

Describe your project's stack to auto-apply the appropriate conventions and load the relevant references.

Frequently Asked Questions about stacks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce ecosystem-specific conventions across multiple stacks?▼

It identifies your active stack by scanning signature files like pyproject.toml, package.json, and go.mod, then loads dedicated reference patterns to enforce ecosystem-specific naming, structure, and dependency guidelines.

What's the best way to scaffold a new Next.js or FastAPI project with idiomatic structure?▼

Scaffolding idiomatic Next.js or FastAPI projects is handled by loading per-stack references that enforce ecosystem-specific directory structures, naming conventions, and configuration guidelines during code generation.

How does stack detection work for Python and Node.js codebases?▼

Stack detection works by scanning for signature files at the repository root, such as pyproject.toml for Python/FastAPI, package.json for Node.js/TypeScript, or next.config.* for Next.js, to determine the active ecosystem.

Can I use this to standardize universal conventions like environment variables and logging?▼

Yes, you can use this to standardize universal conventions. It applies ecosystem-agnostic rules for environment variables, lockfiles, README files, and structured logging at the repository root across all detected stacks.

Does the scaffolding workflow support Go and TypeScript project structures?▼

Yes, the scaffolding workflow supports Go and TypeScript project structures. It loads dedicated references for Node.js/TypeScript and Go to enforce idiomatic structure, dependencies, and configuration during project generation.