agentleFS
evancaevanca/flutter-ai-rules/skills/firebase-storage/SKILL.md

firebase-storage

Skill669 starsChanged 3 months agoMITView on GitHub

Use when setting up Storage, uploading/downloading files, managing metadata, handling errors, or applying security rules.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when:

    line 13
  2. Very specific:

    Run flutterfire configure to update your Firebase config with the default Storage bucket name.

    line 37
  3. Distinctive:

    Use custom metadata to store additional key/value pairs with your files.

    line 100
  4. Very specific:

    Use try-catch with FirebaseException.

    line 106
  5. Distinctive:

    Use Cloud Storage with Firestore for comprehensive data management.

    line 137
  6. Distinctive:

    Use the Firebase Local Emulator Suite for local development and testing.

    line 138
  7. Distinctive:

    Use Firebase Security Rules to control access to files.

    line 144
  8. Distinctive:

    Test security rules thoroughly before deploying to production.

    line 146

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Firebase Cloud Storage Skill

This skill defines how to correctly use Firebase Cloud Storage in Flutter applications.

When to Use

Use this skill when:

  • Setting up Cloud Storage in a Flutter project.
  • Uploading or downloading files.
  • Managing file metadata.
  • Handling Storage errors and monitoring upload progress.

1. Setup and Configuration

flutter pub add firebase_storage
import 'package:firebase_storage/firebase_storage.dart';

final storage = FirebaseStorage.instance;
// Or specify a bucket explicitly:
// final storage = FirebaseStorage.instanceFor(bucket: "gs://BUCKET_NAME");
  • Firebase Storage requires the Blaze (pay-as-you-go) plan.
  • Run flutterfire configure to update your Firebase config with the default Storage bucket name.

Security note: By default, a Cloud Storage bucket requires Firebase Authentication for any action. Configuring public access may also make App Engine files publicly accessible — restrict access again when you set up Authentication.


2. File Operations

Create a reference:

final storageRef = FirebaseStorage.instance.ref();
final fileRef = storageRef.child("uploads/file.jpg");

Upload:

final uploadTask = fileRef.putFile(file);
final snapshot = await uploadTask;
final downloadUrl = await snapshot.ref.getDownloadURL();

Download (in-memory):

final data = await fileRef.getData();

Download URL:

final downloadUrl = await fileRef.getDownloadURL();

Delete:

await fileRef.delete();

3. Metadata Management

Get metadata:

final metadata = await fileRef.getMetadata();
print('Content type: ${metadata.contentType}');
print('Size: ${metadata.size}');

Update metadata:

final newMetadata = SettableMetadata(
  contentType: "image/jpeg",
  customMetadata: {'uploaded_by': 'user123'},
);
await fileRef.updateMetadata(newMetadata);

Use custom metadata to store additional key/value pairs with your files.


4. Error Handling

Use try-catch with FirebaseException. Key error codes:

CodeMeaning
storage/object-not-foundFile doesn't exist at the reference
storage/bucket-not-foundNo bucket configured for Cloud Storage
storage/project-not-foundNo project configured for Cloud Storage
storage/quota-exceededStorage quota exceeded
storage/unauthenticatedUser needs to authenticate
storage/unauthorizedUser lacks permission
storage/retry-limit-exceededOperation timeout exceeded
  • For quota-exceeded on the Spark plan, upgrade to Blaze.
  • Implement retry logic for network-related errors and timeouts.

5. Performance and Best Practices

Monitor upload progress:

final uploadTask = fileRef.putFile(file);
uploadTask.snapshotEvents.listen((TaskSnapshot snapshot) {
  print('Progress: ${(snapshot.bytesTransferred / snapshot.totalBytes) * 100}%');
});
  • Cancel uploads with uploadTask.cancel().
  • Pause / resume with uploadTask.pause() and uploadTask.resume().
  • Optimize file sizes before upload to reduce costs and improve performance.
  • Use Cloud Storage with Firestore for comprehensive data management.
  • Use the Firebase Local Emulator Suite for local development and testing.

6. Security

  • Use Firebase Security Rules to control access to files.
  • Combine Storage rules with Firebase Authentication for user-based access control.
  • Test security rules thoroughly before deploying to production.

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.