Coding
PromptBeginner5 minmarkdown
Markdown Converter
Agent skill for markdown-converter
7
Use Node.js 18 or newer and install dependencies with `pnpm` (enforced by `preinstall`). Run `pnpm install` from the repo root to link workspace packages and set up local post-install patches via `tw-patch`.
Sign in to like and favorite skills
Use Node.js 18 or newer and install dependencies with
pnpm (enforced by preinstall). Run pnpm install from the repo root to link workspace packages and set up local post-install patches via tw-patch.
Source lives in
packages/, with @tailwindcss-mangle/core providing the transformation engine, shared for cross-package utils, config for preset defaults, tailwindcss-patch to shim Tailwind versions, and unplugin-tailwindcss-mangle for build-tool integrations. Example applications live under apps/ for framework-specific smoke tests, while website/ hosts the Astro-powered docs. Reusable scripts live in scripts/, and assets used by docs and samples are under assets/.
pnpm dev: start package-level dev modes across the workspace (e.g., watch builds).pnpm build: run Turbo builds for every package in packages/*.pnpm build:docs: build the Astro documentation site in website/.pnpm lint: apply ESLint fixes across TypeScript sources.pnpm script:clean: remove generated artifacts via the monorepo helper.The codebase is TypeScript-first with strict ESM modules. Formatting is handled by the shared
@icebreakers/eslint-config and Prettier defaults (2-space indentation, semicolons omitted). Prefer PascalCase for exported classes (e.g., ClassGenerator) and camelCase for functions and variables. Keep filenames lowercase with dashes or dots (css/index.ts, test/utils.ts).
Vitest drives unit tests via
vitest.config.ts, discovering suites inside each package’s test/ directory. Name files *.test.ts and keep snapshots in __snapshots__/. Run the full suite with pnpm test; use pnpm test:dev for focused watch mode, or filter with pnpm --filter @tailwindcss-mangle/core test. Coverage is enabled by default and stored in coverage/ directories.
Follow Conventional Commits enforced by Commitlint (e.g.,
feat(core): add selector mangling). Group related changes per package and mention affected workspace names in the scope. Open pull requests with a concise summary, testing notes, and links to any tracking issues. Include screenshots or CLI output when altering developer tooling or docs. Use Changesets (pnpm release) when preparing published releases.
Changesets orchestrate versioning (
pnpm publish-packages). Turbo caches builds, so clear with pnpm script:clean if results look stale. Renovate keeps dependencies current; note any pinning decisions in the PR description.