RuleStack

Configs

Stacks

Compare

Diff

RuleStack

Configs

Stacks

Compare

Diff

Read API

RuleStack

Configs

Stacks

Compare

Diff

Read API

Diff/v1truv1us-fasten-cursor-rules-teaching ↔ v1truv1us-fasten-cursor-rules-security

Comparison

A · Cursor rules · v1truv1us/fastenB · Cursor rules · v1truv1us/fasten
What each file covers, counted
DimensionSharedOnly in AOnly in BOverlap
Sections0160%
Commands0010%
Section tags0040%

What each file covers

Sections

0 shared · 1 only in A · 6 only in B
  • − Teaching and Learning Approach (Severity: Warning)
  • + Security Rules for Fasten
  • + Input Validation
  • + Build & Runtime Security
  • + Reporting Vulnerabilities
  • + User Best Practices
  • + Hardening

Commands

0 shared · 0 only in A · 1 only in B
  • + zig build -Doptimize=ReleaseSafe

Section tags

0 shared · 0 only in A · 4 only in B
  • + build
  • + code-style
  • + security
  • + do-not

Line diff

+26 added−11 removed5 unchanged16.1% identical
v1truv1us/fasten · .cursor/rules/teaching.mdc
@@ −3 @@
3globs:
4alwaysApply: true
5---
6## Teaching and Learning Approach (Severity: Warning)
7- Act as a guide and teacher, not a code writer
8- Explain concepts clearly with examples and reasoning
9- Break down complex topics into digestible steps
10- Show patterns and syntax to follow, but let user implement
11- Focus on "why" and "how" rather than just "what"
12- Ask guiding questions to help user think through design decisions
13- Help debug and troubleshoot when user gets stuck
14- Avoid writing complete implementations or large code blocks
15- Encourage incremental learning and experimentation
16- Provide conceptual examples, not production code to copy-paste
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
v1truv1us/fasten · .cursor/rules/security.mdc
@@ +3 @@
3globs:
4alwaysApply: true
5---
6# Security Rules for Fasten
7 
8## Input Validation
9- Validate all file paths to prevent traversal.
10- Limit input file size and check permissions.
11- Validate and sanitize all input before processing.
12 
13## Build & Runtime Security
14- Use only Zig stdlib; audit any external dependencies.
15- Reproducible, signed builds; secure distribution.
16- Strict memory management; bounds checking; safe allocations.
17- No sensitive info in error messages or logs.
18 
19## Reporting Vulnerabilities
20- Do NOT report via public issues. Email security@fasten-bundler.dev with details.
21- Acknowledge within 48h, resolve critical issues within 30 days.
22 
23## User Best Practices
24- Only process trusted files; verify file integrity.
25- Run in sandbox for untrusted input.
26- Keep system/tools updated; secure storage and access.
27 
28## Hardening
29- Build with `zig build -Doptimize=ReleaseSafe`.
30- Use resource limits (ulimit) and minimal permissions for runtime.
31 
@@ −3 +3 @@
33 globs:
44 alwaysApply: true
55 ---
6−## Teaching and Learning Approach (Severity: Warning)
7−- Act as a guide and teacher, not a code writer
8−- Explain concepts clearly with examples and reasoning
9−- Break down complex topics into digestible steps
10−- Show patterns and syntax to follow, but let user implement
11−- Focus on "why" and "how" rather than just "what"
12−- Ask guiding questions to help user think through design decisions
13−- Help debug and troubleshoot when user gets stuck
14−- Avoid writing complete implementations or large code blocks
15−- Encourage incremental learning and experimentation
16−- Provide conceptual examples, not production code to copy-paste
6+# Security Rules for Fasten
7+ 
8+## Input Validation
9+- Validate all file paths to prevent traversal.
10+- Limit input file size and check permissions.
11+- Validate and sanitize all input before processing.
12+ 
13+## Build & Runtime Security
14+- Use only Zig stdlib; audit any external dependencies.
15+- Reproducible, signed builds; secure distribution.
16+- Strict memory management; bounds checking; safe allocations.
17+- No sensitive info in error messages or logs.
18+ 
19+## Reporting Vulnerabilities
20+- Do NOT report via public issues. Email security@fasten-bundler.dev with details.
21+- Acknowledge within 48h, resolve critical issues within 30 days.
22+ 
23+## User Best Practices
24+- Only process trusted files; verify file integrity.
25+- Run in sandbox for untrusted input.
26+- Keep system/tools updated; secure storage and access.
27+ 
28+## Hardening
29+- Build with `zig build -Doptimize=ReleaseSafe`.
30+- Use resource limits (ulimit) and minimal permissions for runtime.
31+ 
RuleStack

Built by

Kynth Studio

Directory

Configs
Stacks
Compare formats
Diff two configs
Best AGENTS.md examples

Formats

AGENTS.md
CLAUDE.md
Cursor rules
Copilot instructions

Reference

Read API
Corpus health
Privacy Policy
Terms

RuleStack

RuleStack

Built by

Kynth Studio

Directory

Configs
Stacks
Compare formats
Diff two configs
Best AGENTS.md examples

Formats

AGENTS.md
CLAUDE.md
Cursor rules
Copilot instructions

Reference

Read API
Corpus health
Privacy Policy
Terms

RuleStack

RuleStack

Built by

Kynth Studio

Directory

Configs
Stacks
Compare formats
Diff two configs
Best AGENTS.md examples

Formats

AGENTS.md
CLAUDE.md
Cursor rules
Copilot instructions

Reference

Read API
Corpus health
Privacy Policy
Terms

RuleStack