Add Kiro AI support with dynamic steering file generation

[ranglang]

No description provided.

[cursor]

Bug: KiroFormatter: Null Checks and Filename Mapping Issues

The KiroFormatter has two issues:

1. rule.name is accessed directly without null/undefined checks (e.g., rule.name.toLowerCase()), which can cause a TypeError if rule.name is undefined. This affects methods like getFileName and isDefaultFile.
2. The getFileName method's logic for mapping rule names to filenames is too broad (e.g., name.includes('product')), causing multiple rules to generate the same filename (e.g., 'product.md'). This results in file overwrites and data loss.

src/formatters/kiro.ts#L100-L121

onlyrules/src/formatters/kiro.ts

Lines 100 to 121 in a1f0482

	*/
	private getFileName(rule: ParsedRule): string {
	// Use standardized names for common rule types
	const name = rule.name.toLowerCase();
	// Map common rule names to Kiro's default files
	if (name.includes('product') || name.includes('overview')) {
	return 'product.md';
	} else if (name.includes('tech') || name.includes('stack') || name.includes('technology')) {
	return 'tech.md';
	} else if (name.includes('structure') || name.includes('architecture')) {
	return 'structure.md';
	}
	// For other rules, use descriptive filenames
	const filename = rule.name
	.toLowerCase()
	.replace(/[^a-z0-9]+/g, '-')
	.replace(/^-|-$/g, '');
	return `${filename}${this.spec.extension}`;
	}

Fix in Cursor • Fix in Web

---

BugBot free trial expires on July 25, 2025
Learn more in the Cursor dashboard.

Was this report helpful? Give feedback by reacting with 👍 or 👎