implement issue12

[arrowkato]

resolve #12

implemented the specifications #12 (comment)

[Copilot]

Pull Request Overview

Adds support for a new cursorRuleType field in frontmatter to distinguish four Cursor rule behaviors (always, manual, specificFiles, intelligently). The PR updates parsing logic, markdown generation, tests, and documentation to implement the Issue #12 specification.

• Introduce cursorRuleType in RuleFrontmatter and propagate it through parsing/generation
• Enhance parseCursorConfiguration and convertCursorMdcFrontmatter to classify MDC/legacy rules into four types
• Update generateCursorMarkdown and its tests to output the new frontmatter format
• Revise core validation and add doc/README updates for Cursor rule types

Reviewed Changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
src/types/rules.ts	Add optional cursorRuleType to RuleFrontmatter
src/parsers/cursor.ts	Implement convertCursorMdcFrontmatter, update parsing
src/parsers/cursor.test.ts	Update parsing tests to expect new rule classifications
src/generators/rules/cursor.ts	Rewrite generateCursorMarkdown, add determineCursorRuleType
src/generators/rules/cursor.test.ts	Extend generator tests for all four rule types
src/core/parser.ts	Allow empty description (relax validation)
README.md / README.ja.md	Document cursorRuleType field and behavior
CONTRIBUTING.md / CONTRIBUTING.ja.md	Note Cursor parser supports four rule types

Comments suppressed due to low confidence (4)

src/parsers/cursor.ts:68

• [nitpick] Each return in convertCursorMdcFrontmatter repeats root and targets. Extract a base object with { root: false, targets: ["*"] } and spread it into each branch to reduce duplication.

    return {

src/generators/rules/cursor.ts:95

• The return type of determineCursorRuleType is declared as string. It should be the union "always"|"manual"|"specificFiles"|"intelligently" (e.g. RuleFrontmatter['cursorRuleType']) to enforce type safety.

function determineCursorRuleType(

src/parsers/cursor.ts:33

• [nitpick] The regex for unquoted glob patterns is complex and brittle. Consider simplifying it or using a YAML loader schema that accepts unquoted strings, and add inline comments explaining each step.

            // But exclude array literals (starting with [ or already quoted strings)

CONTRIBUTING.md:105

• [nitpick] The comment about supporting four rule types is misaligned under the file tree. Move it to the end of the cursor.ts line so it clearly annotates that file.

│   │   │                  # Supports 4 rule types: always, manual, specificFiles, intelligently

[dyoshikawa]

@arrowkato Thank you!

[arrowkato]

Thank you for your review!