Coding
PromptBeginner5 minmarkdown
Markdown Converter
Agent skill for markdown-converter
21
Sign in to like and favorite skills
dev – Start dev server
npm run dev (or yarn dev)
build – Build production assets
npm run build
preview – Preview local build
npm run preview
lint – Run ESLint (if configured)
npx eslint . --ext .js,.vue
(install ESLint first if missing: npm i -D eslint)
test – Run all Vitest tests
npx vitest
test:one – Run a single test file (replace
Path/To/Test.vue)
npx vitest src/__tests__/Path/To/Test.vue
| Topic | Guideline |
|---|---|
| Imports | Keep external imports at the top, sorted alphabetically. Local relative imports follow. Separate groups by a blank line. |
| Formatting | Use Prettier (installed via ) – . Two‑space indent, single quotes, trailing commas where possible. |
| Type‑Safety | Add JSDoc types or TypeScript (/). When using Vue 3, define component props/types in . |
| Naming | - Components: PascalCase (). - Variables/Props: camelCase. - Constants: UPPER_SNAKE_CASE. |
| Error Handling | Prefer around async API calls; log errors to console and surface user‑friendly messages using or Snackbar. |
| Testing | Write tests in with the same relative path as the source file. Use – snapshots for component rendering. |
| Linting | Enforce no‑undef, no‑unused-vars, and camelcase rules. Add a if missing. |
| Commit style | Conventional commits (, , ) – not mandatory but recommended. |
(None currently found. Add rules in
or .cursor/rules/
if needed.).cursorrules
Tip: Run
npm run dev then hit Ctrl+C to exit; repeat for preview/build. Use npx vitest to run all tests. For a single file, pass the path to the test as shown above.